登录
HazAT

commit

by @HazAT in Development
0
0
# Install this skill:
npx skills add HazAT/pi-config --skill "commit"

Install specific skill from multi-skill repository

# Description

Read this skill before making git commits

# SKILL.md

name: commit
description: "Read this skill before making git commits"
license: From mitsuhiko/agent-stuff

Create a git commit for the current changes using a concise Conventional Commits-style subject.

Format

<type>(<scope>): <summary>

  • type REQUIRED. Use feat for new features, fix for bug fixes. Other common types: docs, refactor, chore, test, perf.
  • scope OPTIONAL. Short noun in parentheses for the affected area (e.g., api, parser, ui).
  • summary REQUIRED. Short, imperative, <= 72 chars, no trailing period.

Notes

  • Body is OPTIONAL. If needed, add a blank line after the subject and write short paragraphs.
  • Do NOT include breaking-change markers or footers.
  • Do NOT add sign-offs (no Signed-off-by).
  • Only commit; do NOT push.
  • If it is unclear whether a file should be included, ask the user which files to commit.
  • Treat any caller-provided arguments as additional commit guidance. Common patterns:
  • Freeform instructions should influence scope, summary, and body.
  • File paths or globs should limit which files to commit. If files are specified, only stage/commit those unless the user explicitly asks otherwise.
  • If arguments combine files and instructions, honor both.

Steps

  1. Infer from the prompt if the user provided specific file paths/globs and/or additional instructions.
  2. Review git status and git diff to understand the current changes (limit to argument-specified files if provided).
  3. (Optional) Run git log -n 50 --pretty=format:%s to see commonly used scopes.
  4. If there are ambiguous extra files, ask the user for clarification before committing.
  5. Stage only the intended files (all changes if no files specified).
  6. Run git commit -m "<subject>" (and -m "<body>" if needed).

# Related Skills

facebook
feature-flags @facebook

Use when feature flag tests fail, flags need updating, understanding @gate pragmas, debugging...

★ 242,571
facebook
fix @facebook

Use when you have lint errors, formatting issues, or before committing code to ensure it passes CI.

★ 242,571
facebook
flags @facebook

Use when you need to check feature flag states, compare channels, or debug why a feature behaves...

★ 242,571

# Supported AI Coding Agents

This skill is compatible with the SKILL.md standard and works with all major AI coding agents:

⚡ Amp 🚀 Antigravity 🤖 Claude Code 🦀 Clawdbot 📝 Codex ▶️ Cursor 🤖 Droid 💎 Gemini CLI 🐙 GitHub Copilot 🪿 Goose 📊 Kilo Code 🔧 Kiro CLI 💻 OpenCode 🦘 Roo Code 🌲 Trae 🏄 Windsurf

Learn more about the SKILL.md standard and how to use these skills with your preferred AI coding agent.