
Commit
- 2 repo stars
- Updated July 24, 2026
- cboone/agent-harness-plugins
Make smart, context-aware git commits with conventional commit messages and awareness of the active plan.
About
Commit makes smart, context-aware git commits that follow the conventional-commits format and stay aware of the active plan. It inspects the staged changes to write a fitting message rather than a generic one. A git workflow helper for keeping commit history clean and structured during development.
- Context-aware commits
- Conventional commit messages
- Plan-aware
- Git workflow helper
Commit by the numbers
- Data as of Jul 25, 2026 (Skillselion catalog sync)
/plugin marketplace add cboone/agent-harness-plugins/plugin install commit@agent-harness-pluginsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| repo stars | ★ 2 |
|---|---|
| Last updated | July 24, 2026 |
| Repository | cboone/agent-harness-plugins ↗ |
What it does
Make smart, context-aware git commits with conventional commit messages and awareness of the active plan.
README.md
Commit
Smart, context-aware git commits with conventional commit messages and plan awareness.
Type: Skill
Trigger: /commit
Installation
See the marketplace install instructions.
What It Does
Analyzes your diff to generate well-structured conventional commit messages that match your repository's existing style. Handles staged-only vs. all changes, supports commit-and-push workflows, and can detect plan files for separate commits.
Usage
/commit
/commit --push
/commit --staged
/commit --plan
/commit --all
| Option | Description |
|---|---|
--push |
Push to remote after committing |
--staged |
Commit only staged changes, ignoring unstaged changes |
--plan |
Commit only the plan file(s) |
--all |
Stage and commit all changes including untracked files |
Recommended Permissions
This skill runs git commands that trigger permission prompts. To allow them automatically, add these rules to your .claude/settings.json (project-wide) or ~/.claude/settings.json (global):
{
"permissions": {
"allow": ["Bash(git status*)", "Bash(git diff*)", "Bash(git log *)", "Bash(git add *)", "Bash(git commit *)", "Bash(git push*)", "Bash(git branch *)", "Bash(git mv *)"]
}
}
If you already have a permissions.allow array, merge these entries into it. Review and adjust the rules to match your security preferences.
Examples
- "commit": stages and commits with an auto-generated message
- "commit and push": commits then pushes to remote
- "commit the plan, then the changes": creates two sequential commits
- "give the plan a meaningful name and commit": renames and commits the plan file
See Also
- PR: commit, push, and open a pull request in one step
- All plugins