·
Last changedVersion:
This version passed the hardening gate. The skill content was retained without changes. Classified findings before hardening: 1. Classified findings closed: 0. Classified findings remaining: 1. Unclassified scanner findings remaining: 0. Review findings closed: 0. Review findings remaining: 7.
1
1
Expand | File | Group | Subtype | Severity | Status |
|---|---|---|---|---|---|
SKILL.md | Prompt Injection | Third-party content as instructions | Low | Open |
1 finding
Write commit messages terse and exact. Conventional Commits format. No fluff. Why over what.
Subject line:
<type>(<scope>): <imperative summary> — <scope> optionalfeat, fix, refactor, perf, docs, test, chore, build, ci, style, revertBody (only if needed):
- not *Closes #42, Refs #17What NEVER goes in:
Assisted-by/AI-attribution trailer, then add it as a trailerDiff: new endpoint for user profile with body explaining the why
Diff: breaking API change
Always include body for: breaking changes, security fixes, data migrations, anything reverting a prior commit. Never compress these into subject-only — future debuggers need the context.
Only generates the commit message. Does not run git commit, does not stage files, does not amend. Output the message as a code block ready to paste. "stop caveman-commit" or "normal mode": revert to verbose commit style.
Get started with chainctlchainctl skill install public/juliusbrussee/caveman-commit:latest
Bring Chainguard's hardening pipeline to your first-party skills — custom rulesets, automated remediation, full audit trail.
skills.cgr.dev/public/github.com/juliusbrussee/skills/caveman-commit:latest
MIT
HARDENING.md
LICENSE
README.md
SKILL.md