Git Conventional Commits
Guide the user and agent to use conventional commits format for git messages. Use this skill when the user asks to "commit changes", "create a release", "explain commit format", or when performing any git commit action.
Install
$ agentstack add skill-michaeld-42-agentic-skills-git-conventional-commits ✓ 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-michaeld-42-agentic-skills-git-conventional-commits) 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 Commits & Semantic Release
Overview
This skill ensures that all git commit messages follow the Conventional Commits specification. This structure enables automated versioning (Semantic Release) and creates a standardized project history.
Core Format
():
[optional body]
[optional footer(s)]Key Rules
- Type: Must be one of the allowed types (see
references/commit-types.md). - Scope: Optional but recommended. Describes the part of the codebase affected (e.g.,
physics,ui,deps). - Description: concise summary in imperative mood ("add" not "added").
- Breaking Changes: Must be indicated by a
!after the type/scope or aBREAKING CHANGE:footer.
When to Use This Skill
- Before running
git commit. - When the user asks to "save changes".
- When explaining why a version number bumped (Semantic Versioning).
Reference Index
1. Allowed Types
> See: references/commit-types.md > > detailed list of types (feat, fix, chore, etc.) and their impact on version numbers.
2. Examples
> See: references/examples.md > > Good and bad examples of commit messages, including breaking changes.
Workflow
- Identify Change: What did you do? (Fix a bug? Add a feature?)
- Determine Impact: Does it break backward compatibility?
- Format Message: Construct the header line
type(scope): description. - Commit: Use the formatted message.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MichaelD-42
- Source: MichaelD-42/agentic-skills
- License: MIT
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.