formatting-commit-messages — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited formatting-commit-messages (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.
git diff --cached<type>[optional scope][!]: <description>
[optional body]
[optional footer(s)]| Type | When to Use |
|---|---|
feat | New feature for the user |
fix | Bug fix for the user |
docs | Documentation only changes |
style | Formatting, missing semicolons (no code change) |
refactor | Code change that neither fixes nor adds feature |
perf | Performance improvement |
test | Adding or correcting tests |
build | Changes to build system or dependencies |
ci | CI configuration changes |
chore | Other changes that don't modify src or tests |
revert | Reverts a previous commit |
! after type/scope: feat(api)!: remove deprecated endpointsBREAKING CHANGE: footer in the bodyRun the following to get staged diffs:
git diff --cached --stat
git diff --cachedAnalyze the changes to determine the appropriate type:
src/ with new functionality → featfix*.md, *.txt, or docs folder → docsstylerefactorperftestpackage.json, webpack.config.*, tsconfig.* → build.github/workflows/, CI configs → cichoreDerive scope from the primary affected area:
src/components/Button.tsx → scope: buttonsrc/api/users.ts → scope: api or userslib/utils/ → scope: utilsLook for indicators of breaking changes:
Subject line rules:
Body (if needed):
Footer (if needed):
BREAKING CHANGE: <description>Fixes #123 or Closes #456Reviewed-by: Name <email>Present the formatted message to the user:
**Suggested commit message:**
feat(auth): add OAuth2 login support
Implement OAuth2 authentication flow with Google and GitHub providers.
Users can now sign in using their existing accounts.
Closes #142If approved, execute:
git commit -m "<subject>" -m "<body>" -m "<footer>"Or for simple commits:
git commit -m "<type>(<scope>): <description>"feat(cart): add quantity selector to cart itemsfix(auth): prevent token refresh race condition
Multiple simultaneous requests could trigger parallel refresh attempts.
Added mutex lock to ensure single refresh execution.
Fixes #287feat(api)!: migrate to v2 response format
BREAKING CHANGE: API responses now use camelCase keys instead of snake_case.
All clients must update their parsing logic.docs(readme): add installation instructions for Windowsrefactor(utils): extract date formatting into separate moduleBefore committing, verify:
git status to confirm. Prompt user to stage files first.git status for conflicts or hooks blocking commit.git commit --help for options.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.