Generate a commit message and commit staged changes using git commit -s -S.
78%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/commit/SKILL.mdCommit the current staged changes.
git diff --staged. If empty, tell the user there is nothing staged and stop.git log --oneline -5 to understand this repo's commit message style.git branch --show-current to get the branch name. If it matches <type>/issue-<number>-<description>, the commit body is Refs linuxfoundation/lfx-cdp-insights-ops#<number>. Otherwise ask the user for the tracking issue number in linuxfoundation/lfx-cdp-insights-ops; if they have none, commit without a body.type: description. Subject max 72 characters, lowercase, no trailing period, no issue reference. No scope required unless meaningful. The only body line is the Refs line from step 3. No extra trailers, no Co-Authored-By. (The Signed-off-by trailer is added automatically by -s.)
feat, fix, docs, style, refactor, perf, test, build, ci, chore, revertgit commit -s -S -m "<subject>" -m "<body>" using exactly the generated message (omit the second -m when there is no body).linuxfoundation/crowd.dev
682285e
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.