Skill

commit-agent

Use when the user asks to commit changes, stage and commit, commit all changes, commit everything, or save their work to git. Does not push or create PRs — use pr-agent for that.

Install

npx claudepluginhub shawn-sandy/agentics --plugin git-agent

Tool Access

This skill is limited to using the following tools:

Bash(git *)

Preview

Stage all changes and create a conventional commit message. Follow these steps in strict order. **STOP immediately after step 4.**

SKILL.md

Similar Skills

using-git-worktrees

Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.

superpowers

158.9k

subagent-driven-development

3 files

Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.

superpowers

158.9k

dispatching-parallel-agents

Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.

superpowers

158.9k

Stats

Parent Repo Stars1

Parent Repo Forks0

Last CommitApr 4, 2026

Used By2 plugins

Actions

View Source View Plugin View on GitHub View README

Stage all changes and create a conventional commit message. Follow these steps in strict order. STOP immediately after step 4.

Step 1: Guards

Run git status to check repository state.

Clean working tree (nothing to commit): output "Nothing to commit — working tree is clean." and STOP.
Detached HEAD (git branch --show-current returns empty): output "Cannot commit: repository is in detached HEAD state. Checkout a branch first." and STOP.

Step 2: Stage Changes

Run git add -A to stage all changes.

This trusts .gitignore to exclude sensitive or generated files. The user is responsible for .gitignore correctness.

Step 3: Analyze Diff and Write Commit Message

Run git diff --staged to inspect all staged changes.

Write a conventional commit message:

<type>(<scope>): <description>

Rules:

Total length: ≤ 72 characters
Types: feat, fix, docs, refactor, test, chore, perf, style, ci, build
Scope: the most-changed top-level directory (e.g., plugins/git-agent → plugins/git-agent)
Omit scope entirely if changes span more than 2 top-level directories
Description: imperative mood, lowercase, no trailing period

Examples:

feat(plugins/git-agent): add commit-agent and pr-agent skills
fix(plugins/code-review): correct activation trigger wording
chore: update marketplace.json with new plugin entry

Step 4: Commit

Run:

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.