bakeoff/fixtures/v4/commit-message/commit-message/SKILL.md
Helps write commit messages.
npx skillsauth add bjg4/bgskillz commit-messageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You should help the user write good commit messages. Commit messages are important for project history and you should take care to write them well.
Good commit messages help teams understand what changed and why. You should always try to write clear and descriptive messages.
You should use the imperative mood. You should keep the subject line under 50 characters if possible. You should add a body if the change needs explanation. You should reference issue numbers when relevant.
You might want to use conventional commits format sometimes. This includes types like feat, fix, docs, etc. You should explain the format if the user is unfamiliar.
You should provide examples of good commit messages when helpful.
You should not write vague messages like "fix stuff" or "update". You should not include unnecessary detail.
Think about what a reviewer would want to know. Consider breaking large changes into multiple commits. Remember that the message is permanent.
development
Create S-tier portable skills and agents with comprehensive quality guidance. Use when creating or improving skills, designing multi-agent orchestration workflows, auditing agent quality, running evals, or learning agent-building best practices. Covers the full lifecycle from use case definition through automated evaluation, review, and iteration. Do NOT use for general coding tasks, writing documentation unrelated to agents/skills, or building applications.
development
Create S-tier portable skills and agents with comprehensive quality guidance. Use when creating or improving skills, designing multi-agent orchestration workflows, auditing agent quality, running evals, or learning agent-building best practices. Covers the full lifecycle from use case definition through automated evaluation, review, and iteration. Do NOT use for general coding tasks, writing documentation unrelated to agents/skills, or building applications.
development
Create S-tier portable skills and agents with comprehensive quality guidance. Use when creating or improving skills, designing multi-agent orchestration workflows, auditing agent quality, running evals, or learning agent-building best practices. Covers the full lifecycle from use case definition through automated evaluation, review, and iteration. Do NOT use for general coding tasks, writing documentation unrelated to agents/skills, or building applications.
development
Stress-test a plan or design through Socratic questioning until shared understanding. Use when the user says "grill me", wants to stress-test a plan, or review a design. Do NOT use for implementation or code generation.