Agent-Skills.md

Agent Skills: Git Commits

Git commit workflow and message format. Use when making commits, asking about commit conventions, or after completing code changes. Enforces atomic commits with structured messages (type/scope/summary + what/why body).

UncategorizedID: iamhenry/ai-project-starter-kit/git-commits
53

Install this agent skill to your local

pnpm dlx add-skill https://github.com/iamhenry/ai-project-starter-kit/tree/HEAD/.agents/skills/git-commits

Skill Files

Browse the full folder contents for git-commits.

Download Skill

Loading file tree…

.agents/skills/git-commits/SKILL.md

Skill Metadata

Name
git-commits
Description
Git commit workflow and message format. Use when explicitly asked to commit or explain commit conventions. Commit only intended files; push only with explicit authority. Uses structured messages (type/scope/summary + what/why body).

Git Commits

WORKFLOW

  1. Confirm the user authorized a commit; explaining conventions or finishing implementation does not authorize publication.
  2. Inspect git status --porcelain, git diff, git diff --cached, and git log --oneline -10. Stage only intended changes with explicit paths. If unrelated changes are already staged, stop and resolve the scope without altering the user's staging silently.
  3. PRE-FLIGHT (before any commit): scan staged diff + filenames for sensitive info
    • What to look for: passwords, API keys, tokens, secrets, private keys, credentials, personal data (emails, phone numbers, names of private individuals), logs, screenshots, session data
    • Scan the diff (git diff / git diff --cached) AND filenames (e.g. debug.log, screenshot.png, notes.txt)
    • Also check untracked files about to be committed
    • If anything sensitive found: STOP, report it, ask the user. Never commit and "fix later". Git history keeps secrets forever.
    • If clean: proceed
  4. Commit only the reviewed staged changes using the format below. Do not use commit-all flags or bypass hooks. If a hook fails, fix the in-scope issue, recheck affected evidence, and retry; do not amend without permission.
  5. Push only when explicitly authorized; a commit request alone is not push authority.
  6. Then stop

Format

<type>(<scope>): <summary>
<body with what changed and why>
  • Title (first line): Required - follows <type>(<scope>): <summary> format
  • Body (after blank line): REQUIRED - for each changed file, add a parent bullet with the file path, then nested bullets for what changed and why.

Example

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

  src/components/button.js
    - What: Added Button with size props.
    - Why: Enable dynamic size adjustments for a customizable UI.

  tests/button.test.js
    - What: Created tests for Button sizing.
    - Why: Ensure reliable rendering and detect regressions.

SCOPE

Specifies area of change:

  • auth, user, dashboard, api, database, ui, transfer, etc.

ANTI-PATTERNS

  • NEVER skip the body - it documents intent