Menu
Create well-formatted commits following conventional commits style with proper atomic commits and descriptive messages
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | git-commit |
| description | Create well-formatted commits following conventional commits style with proper atomic commits and descriptive messages |
Use this skill when:
NEVER STAGE OR UNSTAGE FILES WITHOUT EXPLICIT PERMISSION
Do NOT run any of these commands WITHOUT user permission:
git addgit stagegit resetgit restore --stagedDefault behavior: Only work with files that are ALREADY staged by the user.
Exception: Only stage files if the user gives explicit permission when asked.
FIRST: Check which files are staged and unstaged with git status. (Do not mix these two categories up!)
ABSOLUTE REQUIREMENT: Do NOT attempt to change what is staged, now or at any later point in this process!
FORBIDDEN COMMANDS: git add, git stage, git reset, git restore --staged, or ANY staging commands WITHOUT explicit user permission!
IF NOTHING IS STAGED: STOP immediately and ask the user: "No files are staged for commit. Would you like me to stage all modified files, or would you prefer to stage specific files yourself? If you want me to stage files, please give explicit permission."
Check historical commits to learn style and tone: git log --oneline -40
Analyze the diff to determine if multiple distinct logical changes are present.
If multiple distinct changes are detected, stop and ask the user whether to break the commit into multiple smaller commits.
Use the output of git diff --cached --no-ext-diff to understand what actual changes are staged. Be careful not to confused staged with unstaged changes.
Commit to git using a descriptive commit message that:
Uses conventional commit format (feat:, fix:, refactor:, etc.) following existing style and tone
Roughly follows this template (wrap the body at 78 columns):
feat: <what changed, keep under 75 characters>
Without this patch, ... <describe the status quo relevant to this change>
This is a problem because ... <describe *why* the change is needed>
This patch solves the problem by ... <describe *how* the solution works>
Lists key changes and additions
References the task number and the task file it came from
Adds a "Co-authored-by:" footer which clarifies which AI agent helped create this commit, using an appropriate noreply@... email address
Use the Xero MCP server — obtain/refresh OAuth2 bearer tokens, troubleshoot authentication, and pick up other operational notes for working with Xero MCP tools. Use when Xero MCP tools fail with authentication errors, when the bearer token has expired (tokens last ~30 min), before starting any Xero workflow, or for general guidance on Xero MCP usage.
General Xero browser automation notes. Use when automating any Xero page with agent-browser — covers non-standard UI patterns, waiting, and dropdown menus.
Size the agent-browser Chromium window to fill its current screen, leaving a configurable bottom margin for the desktop panel. Use before any agent-browser automation that needs the full screen visible without elements overlapping or scrolling off (e.g. Xero, dense web apps).
Review all unreviewed documents in Hubdoc. Use when reviewing, processing or publishing Hubdoc receipts and bills.
Convert XLSX spreadsheets (single or multi-sheet) to CSV files you can read and grep. Use whenever you need to process an .xlsx report from Xero, Cryptio, bank exports, or any tool that delivers spreadsheet output.
Create Claude Code slash commands, OpenCode command files, and Pi prompt templates that delegate to the right subagent or skill. Use when creating new commands or refactoring existing ones to follow platform conventions.