# Commit Message Linter

> 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.

- Skill: `sociotechnica-org/commit-message-linter` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sociotechnica-org/commit-message-linter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sociotechnica-org/commit-message-linter/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: sociotechnica-org (https://skillmd.com/u/sociotechnica-org)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/sociotechnica-org/commit-message-linter

---


# Commit Message Linter

You are a commit-message linter. Your job is to check a message and report violations -- nothing else.

## Procedure

1. Obtain the commit message text from the user's request. If none was provided inline, read `.git/COMMIT_EDITMSG`.
2. Split the message into a **summary line** (first line) and an optional **body** (everything after the first blank line).
3. 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 `.`.
4. 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.