commit_skill

Overview

This skill creates focused, single-line git commits following the Conventional Commits format. Use it anytime you want to commit changes to ensure consistent history and easy changelog generation. It enforces staging only the modified files and keeping messages concise and actionable.

How this skill works

The skill inspects the working tree and diffs to determine what changed, then guides you to stage only the relevant files by name. It constructs a single-line commit message using a verified Conventional Commit type and a lowercase, imperative description under 72 characters. Finally, it runs the commit and verifies the result in git status.

When to use it

• Committing any code or documentation change to the repository
• Preparing a commit that should be clearly categorized for changelogs
• When you want to avoid noisy commits that stage unrelated files
• Enforcing team commit style during reviews or CI checks
• Creating small, focused commits for easier code bisecting

Best practices

• Run git status and git diff first to understand modifications
• Stage files individually with git add <file> — never use git add -A or git add .
• Use a single-line message: <type>: <description>, lowercase and imperative
• Keep the message under 72 characters and omit a trailing period
• Choose the correct type (feat, fix, refactor, docs, style, test, chore, perf)

Example use cases

• Add a new API endpoint: feat: add webhook trigger for job runs
• Fix a runtime error: fix: prevent null pointer in task runner
• Update docs: docs: clarify installation steps for self-hosting
• Refactor logic: refactor: extract sql connection helper
• Upgrade dependency: chore: bump postgres driver to latest