reference conventional commits
Enforce Conventional Commits 1.0 standards for git history, PR titles, and automated changelogs.
Free
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsreference conventional commits
Example session with this skill installed
I just added a new column called dismissed_at to the signal table and created a use case to handle it. Write a commit message for this.
- Read your context and instructions
- Compiled the reference conventional commits
I have drafted a conventional commit message for your changes to the signal module.
Commit Message
feat(signal): add dismissed_at column and dismiss use case
Adds a new timestamp column to the signal table to track when a user
dismisses a notification. The associated use case handles the
persistence logic and ensures the dismissed state is reflected in
downstream queries.
Refs #42
Next steps
- Run
git commit -mfollowed by the message above. - Verify the
signalscope matches your project's naming convention for the backend layer. - Ensure no other logical changes (like bug fixes) were included in this specific commit.
Connects securely to your tools. The creator never sees your data.
About this skill
Git history becomes a mess when every developer uses a different naming convention. This skill enforces the Conventional Commits 1.0 standard to ensure your logs remain readable, searchable, and compatible with automated tooling.
What it does
- Standardizes types by mapping changes to specific categories like
feat,fix,refactor, orchore. - Enforces formatting including imperative mood, lowercase subjects, and character limits.
- Identifies scopes to clearly mark which module or feature a commit affects.
- Structures bodies to focus on the "why" behind a change rather than the "what".
- Flags breaking changes using both the
!subject modifier and theBREAKING CHANGE:footer.
How it works
- Analyze changes: Provide a diff or describe the work completed.
- Select type and scope: The skill maps the work to the correct conventional category.
- Draft message: It generates a subject line under 72 characters and an optional explanatory body.
- Review and refine: Compare the draft against the checklist for imperative mood and logical separation.
Frameworks & tools
This skill follows the Conventional Commits 1.0 specification. It is compatible with any git-based workflow and tools that consume conventional logs, such as semantic-release, standard-version, and automated changelog generators.
Why this beats prompting it yourself
Writing consistent commit messages manually is prone to "lazy" descriptions like "updated files." This skill provides a strict reference for type mapping and formatting rules that most general-purpose prompts overlook, such as DCO sign-offs and proper breaking change markers.
Use cases
- Drafting clean commit messages for complex multi-file refactors.
- Standardizing PR titles to ensure squash-merges maintain a readable log.
- Generating structured entries for automated changelog tools.
- Auditing existing commit drafts to ensure they follow repo standards.
Known limitations
This skill does not interact with the git CLI directly. It generates the text for you to paste into your terminal or IDE.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean today
- Free to download with an account
Requires
Git