Conventional Commit
Draft a Conventional Commit message when the user requests a commit or message. Formats only; does not authorize Git operations.
Install
$ agentstack add skill-bnet47-codexicon-conventional-commit ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README — it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-bnet47-codexicon-conventional-commit) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming — see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps — measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Conventional commit
Format:
type(scope): imperative summaryAllowed types: feat, fix, docs, refactor, test, chore, perf, ci, build, revert.
- Derive the scope from the behavior or module, not the ticket name.
- Use lowercase imperative wording with no trailing period.
- Keep the subject at or below 72 characters when practical.
- Add a body when motivation, migration, compatibility, or risk is not obvious from the diff.
- Add
BREAKING CHANGE:only for an intentional incompatible change.
Inspect the staged diff before finalizing the message. If nothing is staged or unrelated changes are mixed together, report that instead of inventing a broad message.
This skill does not stage files, create a commit, push, or open a PR unless the user explicitly requested those operations through $ship or an equivalent instruction.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: bnet47
- Source: bnet47/codexicon
- License: MIT
- Homepage: https://bnet47.github.io/codexicon/repo-template-playbook.html
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.