Generate Conventional Commits messages from staged Git changes.
npx skills add https://github.com/reidemeister94/development-skills --skill commit-reidemeister94
Please help me install this Agent Skill. Skill: commit Source: https://github.com/reidemeister94/development-skills/tree/main/skills/commit Command: npx skills add https://github.com/reidemeister94/development-skills --skill commit-reidemeister94
Writing consistent, descriptive commit messages is error-prone and time-consuming when using standard diffs; this Skill automates the process by inspecting staged changes and producing a Conventional Commits subject, with an optional body for breaking changes or non-obvious reasoning.
Review the staged changes with git diff --cached and the recent history with git log --oneline -5, then write a Conventional Commits subject, commit, and verify the result.
High-intent search queries and answers about installing and using this skill.
To generate conventional commit messages from staged git changes, inspect the diff with git diff --cached and recent history with git log --oneline -5, then automatically craft a subject and optional body for breaking changes before committing and verifying the result.
Automating commit message formatting for version control involves inspecting staged changes to produce a Conventional Commits subject and adding a body for non-obvious reasoning or breaking changes to ensure disciplined history for features, fixes, and chores.
To add a body for breaking changes when writing conventional commits, analyze the staged diff and recent log history, then append a body explaining non-obvious reasoning or breaking changes to the generated subject before executing the commit.
No, automated commit generation does not add AI-attribution trailers like Co-Authored-By to the git log because it enforces commit hygiene rules that explicitly reject adding these trailers during the commit verification process.
Yes, you can use automated conventional commits with standard git workflows because it applies to typical Git workflows requiring disciplined history, inspecting staged changes and recent logs to commit and verify results without needing additional dependencies.
You should avoid git status -uall when automating conventional commits because the process enforces strict commit hygiene rules that explicitly prohibit using -uall, ensuring clean version control automation without untracked file noise.
anshul-garg27Identify code changes from diffs, PRs, or branches and run parallel security, performance, and quality reviews.
t0labAnalyze Conventional Commits to draft changelogs and create release commits and tags.
docaohieu2808Stage, commit, push, and merge branches with conventional commits and security scanning.
y1feng200156Generate Conventional Commits messages from staged Git changes.
