git-add-commit

Automate commit message generation by analyzing your staged changes with git diff to extract the scope of modifications, then create a concise subject line (≤50 characters) and detailed description based on detected patterns, reducing manual effort and ensuring consistent, descriptive commits.

Yes, you can stage all changes or target specific files using git add, then generate a conventional commit message automatically. The Skill analyzes diffs to produce a subject line and bullet-point description, then executes git commit and verifies the result with git log.

Use automated commit message generation based on actual code diffs rather than manual typing. By inspecting git status and git diff to determine what changed, the Skill produces conventional format messages (feat, fix, docs) that accurately reflect the scope of your modifications.

After executing git commit with the generated message, the Skill verifies the commit by running git log -1 to display the last commit details and git status to confirm the working directory state, ensuring the commit was staged and applied as intended.

Yes, the Skill relies on Bash and standard git commands (git status, git diff, git add, git commit, git log) to automate staging and commit message generation, making it compatible with existing shell scripts and CI/CD pipelines.

Use automated commit messages when you want to reduce friction after completing features, ensure consistent formatting across your team, or integrate commits into larger automation workflows. Manual messages remain valuable for complex, multi-faceted changes requiring narrative context beyond diff analysis.