bjg4/commit-message
bakeoff/fixtures/v5/commit-message/commit-message/SKILL.md
Write clear conventional commit messages from git diffs or change descriptions. Use when committing, writing commit messages, or summarizing staged changes. Do NOT use for PR descriptions or release notes.
$ 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 AM101.1s1 file scanned
SKILL.md
- name:
- commit-message
- description:
- Write clear conventional commit messages from git diffs or change descriptions. Use when committing, writing commit messages, or summarizing staged changes. Do NOT use for PR descriptions or release notes.
Commit Message
Quick start
From the diff or change summary, produce:
- Subject: imperative, ≤72 chars, conventional type if clear (
feat:,fix:,docs:) - Body (optional): what and why, wrapped at 72 chars
Conventional commits
| Type | When | |------|------| | feat | New capability | | fix | Bug fix | | docs | Documentation only | | refactor | Behavior-preserving restructure |
Default to feat or fix when obvious; otherwise omit prefix and write a clear subject.
Error handling
If no diff or summary provided, ask for git diff --staged output or a one-line change description.
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