fnl-commit-messages
Installation
SKILL.md
Commit messages
What goes in a commit
- Atomic: one logical change per commit, buildable on its own where the project expects that. Split unrelated edits; keep a change and its tests together. One commit holds one whole seam, not one file or one edit, so neither split a seam into fragments nor merge unrelated seams into one.
- Stage explicit paths. Leave out secrets, env files, credentials, and incidental build, cache or tool output. Generated files that the repository tracks are regenerated and verified the way the repository prescribes.
- Dependency changes pin versions and include the lockfile.
- Preserve other people's uncommitted work: commit only what this task changed.
The message
- Subject: imperative and verb-led (
Add,Fix,Remove,Rename), about 50 characters, no trailing period. It completes "This commit will …". - Attribution: a commit holding another agent's accepted work says so in its body, for example "Written by from a coordinator brief; checked by the coordinator."
- Body when the why is not obvious: the reason, the consumer impact, and any follow-up, in about six lines or fewer, wrapped at about 72 columns; never a list of the files changed or a retelling of the diff. Reference task or issue IDs the project tracks.
- Follow a convention the repository already uses (for example Conventional Commits) over this default.
- End with the attribution trailer the host asks for, exactly as given, and only that one.