conventional-commits — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited conventional-commits (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Enforces the Conventional Commits specification for all git commit messages within this repository. This standard provides a lightweight convention on top of commit messages, ensuring a clear and machine-readable commit history which facilitates automated versioning and changelog generation.
All commit messages must follow this structural pattern:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]You must use one of the following types to categorize your changes:
feat(parser): add ability to parse arrays.! after the type/scope, or by including BREAKING CHANGE: at the beginning of the footer section. A breaking change can be part of a commit of any type.Before finalizing a commit, verify that it adheres to this specification. If using an automated tool or agent to commit, ensure it is configured to follow these rules strictly.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.