kevinslin/dev.conventional-commits
active/dev.conventional-commits/SKILL.md
Draft, validate, or explain Conventional Commit messages.
$ install --global
skillsauthnpx skillsauth add kevinslin/skills dev.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 10, 2026, 7:11 AM196.7s1 file scanned
SKILL.md
- name:
- dev.conventional-commits
- description:
- Draft, validate, or explain Conventional Commit messages.
Conventional Commits Guide
Core format
Use this structure:
<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]
- type: required; categorize the change.
- scope: optional; parenthesized area of the codebase.
- !: optional; mark a breaking change in the header.
- description: required; short, imperative summary.
- body: optional; longer explanation, wrap at ~72 chars.
- footer: optional; metadata and breaking-change notes.
Types
Use feat and fix at minimum:
feat: new feature (minor version bump)fix: bug fix (patch version bump)
Common additional types (only use if the repo allows):
build,chore,ci,docs,perf,refactor,revert,style,test
Breaking changes
Mark breaking changes in one of two ways:
- Add
!after type/scope:feat!: drop Node 16 support
- Add a footer:
BREAKING CHANGE: remove legacy auth endpoints
Breaking changes imply a major version bump.
Reverts
Use the conventional format:
revert: <summary of reverted commit>
This reverts commit <hash>.
Examples
feat(parser): add support for markdown tables
fix: handle empty config file
feat!: replace legacy auth flow
BREAKING CHANGE: legacy auth endpoints removed
docs(readme): add migration notes
Usage checklist
- Identify the change intent (feature, fix, docs, refactor, etc.).
- Decide whether a scope adds clarity; omit if it does not.
- Write a concise, imperative description.
- Add a body if you need rationale, tradeoffs, or migration notes.
- Add
!orBREAKING CHANGE:when the change is breaking.
Related Skills
kevinslin/dev.shortcuts
development
VerifiedTrustedCommunity
Resolve explicit shortcut triggers and usage. Always read this file at the start of a thread or when user mentions `trigger`.
13SKILL.mdUpdated Apr 6, 2026
kevinslin/ag-learn
testing
VerifiedTrustedCommunity
Improve skills from observed agent friction in sessions, PRs, or audits.
13SKILL.mdUpdated Apr 6, 2026
kevinslin/slack-report
development
VerifiedTrustedCommunity
Generate incremental Slack digests for channels, topics, and categories.
9SKILL.mdUpdated May 29, 2026
kevinslin/claw-score
testing
VerifiedTrustedCommunity
Audit an OpenClaw maturity-scorecard surface into an evidence-backed component score report. Use when given a surface from an OpenClaw maturity-scorecard.md and asked to score coverage, quality, readiness, or generate a detailed surface report plus per-component subreports.
9SKILL.mdUpdated May 29, 2026