القائمة
Stages all changes and creates a conventional commit message. Analyzes the diff and writes a descriptive, scope-correct commit. Use when the user asks to commit or save work to git.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Marks a plan as completed. Verifies codebase evidence, ticks acceptance criteria, and re-renders the HTML; --all sweeps unmarked plans. Use via /plan-agent:finalize-plan.
Generates HTML implementation-plan documents. Produces a self-contained .html plan file with steps, acceptance criteria, and metadata. Use when the user asks to create or generate an HTML plan file.
Stress-tests plan decisions node-by-node with focused questions. Walks each decision point surfacing assumptions and weak spots. Use when the user asks to deep grill or stress-test a plan.
Generates a prose reference doc from a completed plan. Inspects the codebase and git history to produce accurate, evidence-backed documentation. Use when the user asks to document a completed plan.
Converts a markdown file into a self-contained HTML page. Produces styled output with syntax highlighting and responsive layout. Use when the user asks to convert a markdown file or plan to HTML.
Writes lifecycle status into a plan's frontmatter, one file or a directory. Inspects codebase and git history for accurate dates. Use when asked to check or update plan status.
| name | commit-agent |
| description | Stages all changes and creates a conventional commit message. Analyzes the diff and writes a descriptive, scope-correct commit. Use when the user asks to commit or save work to git. |
| allowed-tools | Bash(git *), ToolSearch, ExitPlanMode |
| disable-model-invocation | true |
| model | haiku |
Stage all changes and create a conventional commit message. Follow these steps in strict order. STOP immediately after step 4.
Does not push or create PRs — use pr-agent for that.
If currently in plan mode, call ExitPlanMode first and silently before any other action — Staging and committing are git mutations and cannot proceed inside plan mode. Skip this step entirely when not in plan mode. ExitPlanMode is a deferred tool — use ToolSearch with select:ExitPlanMode first, then call it silently.
Run git status to check repository state.
git branch --show-current returns empty): output "Cannot commit: repository is in detached HEAD state. Checkout a branch first." and STOP.Run git add -A to stage all changes.
This trusts .gitignore to exclude sensitive or generated files. The user is responsible for .gitignore correctness.
Run git diff --staged to inspect all staged changes.
Write a conventional commit message:
<type>(<scope>): <description>
Rules:
feat, fix, docs, refactor, test, chore, perf, style, ci, buildplugins/git-agent → plugins/git-agent)Examples:
feat(plugins/git-agent): add commit-agent and pr-agent skillsfix(plugins/code-review): correct activation trigger wordingchore: update marketplace.json with new plugin entryRun:
git commit -m "<message>"
Output the commit hash and message on success.
If a pre-commit hook fails: report the hook's output verbatim and STOP. Do not retry. Do not use --no-verify. Do not modify the staged files. Let the user fix the issue.
After a successful commit, output one line:
To undo:
git reset HEAD~1
STOP here. Do not run tests, analyze coverage, check for issues, push, create PRs, or take any further action.