commit-messages
Writes commit messages in this repo's conventional-commit style
Source facts
- Repository
- harehare/minder
- Last source activity
- July 4, 2026 at 02:19
- Detected SKILL.md language
- English
- Stars
- 0
- Forks
- 0
Install options
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Review the source files
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Showing SKILL.md
SKILL.md
Source instructions · Read-only preview- name
- commit-messages
- description
- Writes commit messages in this repo's conventional-commit style
# Commit messages
Use Conventional Commits: `<type>(<scope>): <summary>`, imperative mood, no
trailing period, summary under 72 characters.
Common types: `feat`, `fix`, `refactor`, `test`, `docs`, `build`, `chore`.
Before writing the message:
1. Run `git diff --staged` (or `git diff` if nothing is staged) to see what
actually changed.
2. Pick the type that matches the *dominant* change -- if a commit both fixes
a bug and adds a test, prefer `fix`.
3. Keep the scope to a single crate or module name when the change is
localized (e.g. `fix(agent-tools): ...`); omit the scope for changes that
span the workspace.
4. Do not describe *what* the diff shows line by line -- summarize the
effect of the change.
View on GitHub