metalagman/conventional-commits
conventional-commits/SKILL.md
Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
$ install --global
skillsauthnpx skillsauth add metalagman/agent-skills conventional-commitsInstall 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: May 7, 2026, 6:18 AM149.7s3 files scanned
SKILL.md
- name:
- conventional-commits
- description:
- Use this skill to write, validate, or generate commit messages that follow the Conventional Commits specification.
- short-description:
- Expert at writing semantic, machine-readable commit messages.
Conventional Commits Expert
You are an expert in the Conventional Commits specification. Your goal is to ensure all commit messages are semantic, structured, and useful for automated changelog generation and versioning.
Core Mandates
- Structure: Every commit MUST follow the
<type>[optional scope]: <description>format. - Imperative Mood: The description MUST be in the imperative mood (e.g., "add" not "added", "fix" not "fixed").
- Lower Case: The type and scope MUST be lower case.
- No Period: The description should NOT end with a period.
Commit Types
- Definitions: See references/types.md for the full list of allowed types (
feat,fix,chore, etc.).
Examples & Patterns
- Good vs. Bad: See assets/examples.md for concrete examples of valid commits.
Workflow
1. Analyzing Changes
Before writing a commit message, analyze the staged changes:
- Is it a new feature? ->
feat - Is it a bug fix? ->
fix - Is it a breaking change? -> Add
!orBREAKING CHANGEfooter.
2. Drafting the Message
Draft the message using the standard format.
- Subject Line: Keep under 50 chars if possible, max 72.
- Body: Wrap at 72 chars. Explain what and why, not how.
3. Verification
Check your draft against the mandates:
- [ ] Correct type used?
- [ ] Scope (optional) describes the module affected?
- [ ] Description is imperative ("add feature")?
- [ ] No trailing period?
Related Skills
metalagman/skill-writer
development
VerifiedTrustedCommunity
Use this skill to design, document, and structure AI agent skills for Gemini, Claude, and Codex. It provides architectural rules, directory standards, and writing best practices.
13SKILL.mdUpdated May 7, 2026
metalagman/omnidist
development
VerifiedTrustedCommunity
Use this skill to initialize, configure, and run omnidist release workflows for Go projects (`init`, `ci`, `build`, `stage`, `verify`, `publish`) including npm and uv publishing setup.
13SKILL.mdUpdated May 7, 2026
metalagman/golangci-lint-strict
development
VerifiedTrustedCommunity
Use this skill to install and use the upstream powerman/golangci-lint-strict config for an exact golangci-lint version by fetching the versioned config file unchanged.
13SKILL.mdUpdated May 7, 2026
metalagman/go-uber-style-guide
development
VerifiedTrustedCommunity
Use this skill to write, refactor, or review Go code according to the Uber Go Style Guide. It ensures strict adherence to correctness, safety, and idiomatic patterns.
13SKILL.mdUpdated May 7, 2026