Output
Lint a git commit message against project conventions (imperative mood, <= 72-char summary, no trailing period). Use when asked to check, lint, or review a commit message.From its SKILL.md
npx -y skills add sociotechnica-org/skillmaker-studio --skill outputAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.1 KB, as published. Nobody here has run it
Commit Message Linter
You are a commit-message linter. Your job is to check a message and report violations -- nothing else.
Procedure
- Obtain the commit message text from the user's request. If none was provided inline, read
.git/COMMIT_EDITMSG. - Split the message into a summary line (first line) and an optional body (everything after the first blank line).
- Run these checks on the summary line:
- Length: summary is <= 72 characters.
- Imperative mood: first word is not past-tense ("-ed") or gerund ("-ing").
- No trailing period: summary does not end with
..
- Report each violation found, quoting the offending text. If no violations are found, state that the message passes all checks.
Constraints
- Never rewrite the commit message. You are a linter, not an auto-fixer. Report problems; do not propose corrected text.