bjg4/commit-message
bakeoff/live/v4/commit-message/commit-message/SKILL.md
Assists developers with writing high-quality commit messages for version control. Use when committing changes, summarizing staged diffs, or preparing changelog entries. Supports conventional commits and descriptive subject lines.
$ install --global
skillsauthnpx skillsauth add bjg4/bgskillz commit-messageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 12, 2026, 3:02 AM98.6s3 files scanned
SKILL.md
- name:
- commit-message
- description:
- Assists developers with writing high-quality commit messages for version control. Use when committing changes, summarizing staged diffs, or preparing changelog entries. Supports conventional commits and descriptive subject lines.
- license:
- MIT
- author:
- bakeoff-v4
- version:
- 1.0.0
Commit Message Skill
Purpose
Good commit messages document what changed and why. Future readers (including future you) rely on history to understand decisions. This skill guides message writing so commits are searchable and meaningful.
Use Cases
- A developer wants to commit staged changes and needs a clear message.
- A team uses conventional commits and wants consistent formatting.
- Someone needs to summarize a complex diff in a readable subject and body.
Why Conventional Commits Help
Standard prefixes (feat, fix, docs, etc.) make history scannable and enable automated tooling. They are not mandatory for every repo but are a strong default when the team adopts them.
Guidelines
Write in imperative mood ("Add feature" not "Added feature") because each commit is a instruction to the repository: "if applied, this commit will..."
Keep the subject line concise — many teams aim for 50–72 characters. Add a body when the why is not obvious from the subject.
Reference issue trackers when the team uses them (e.g., Fixes #123).
Conventional Commit Types
| Type | Purpose | |------|---------| | feat | New user-facing capability | | fix | Bug fix | | docs | Documentation only | | refactor | Code change without behavior change | | test | Tests only | | chore | Maintenance, deps, tooling |
Process
- Read the diff or change summary the user provides.
- Identify the primary intent (feature, fix, docs, etc.).
- Draft subject line; add body if needed.
- Confirm format matches team conventions if known.
Error Handling
If no diff or summary is provided, ask for git diff --staged or a short description of changes.
Examples
Subject: feat(auth): add JWT login endpoint
Subject: fix(api): handle null user in profile lookup
Weak: update stuff — too vague for history search.
Related Skills
bjg4/bgskillz
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated Jun 12, 2026
bjg4/bgskillz
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated Jun 12, 2026
bjg4/bgskillz
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated Jun 12, 2026
bjg4/grill-me
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated Jun 12, 2026