Conventional Commit
- 218 installs
- 2 repo stars
- Updated July 24, 2026
- ilteoood/harness
This is a copy of conventional-commit by github - installs and ranking accrue to the original listing.
Turn messy `git diff` output into Conventional Commits messages and run `git commit` with a consistent type/scope/body structure.
About
Conventional Commit is an agent skill that walks you through inspecting staged changes and encoding them as Conventional Commits—`type(scope): description` plus optional body and breaking-change footer. Solo and indie builders use it whenever they want git history that release tools, changelogs, and teammates can parse without decoding free-form chat. The skill pairs procedural steps (`git status`, diff review, staging) with an XML-shaped message scaffold so the agent does not invent vague one-liners. It is especially useful when you ship often from a single repo and need consistent scopes across frontend, API, and CI tweaks. It is not a linter or commitizen hook; it is prompt-and-workflow guidance that ends in an explicit `git commit` command pattern. Use it during active feature work and again before opening or updating a pull request.
- Structured XML template for type, scope, description, optional body, and BREAKING CHANGE footer
- Workflow: `git status` → `git diff` / `git diff --cached` → stage → compose message
- Supports feat, fix, docs, style, refactor, perf, test, build, ci, chore, and revert types
- Integrated-terminal `git commit -m` step documented for agent-driven commits
- Aligns messages with the Conventional Commits specification for semver tooling
Conventional Commit by the numbers
- 218 all-time installs (skills.sh)
- +30 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 25, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ilteoood/harness --skill conventional-commitAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 218 |
|---|---|
| repo stars | ★ 2 |
| Security audit | 2 / 3 scanners passed |
| Last updated | July 24, 2026 |
| Repository | ilteoood/harness ↗ |
What it does
Turn messy `git diff` output into Conventional Commits messages and run `git commit` with a consistent type/scope/body structure.
Files
Instructions
<description>This file contains a prompt template for generating conventional commit messages. It provides instructions, examples, and formatting guidelines to help users write standardized, descriptive commit messages in accordance with the Conventional Commits specification.</description>Workflow
Follow these steps:
1. Run git status to review changed files. 2. Run git diff or git diff --cached to inspect changes. 3. Stage your changes with git add <file>. 4. Construct your commit message using the following XML structure. 5. After generating your commit message, Copilot will automatically run the following command in your integrated terminal (no confirmation needed):
git commit -m "type(scope): description"6. Just execute this prompt and Copilot will handle the commit for you in the terminal.
Commit Message Structure
<commit-message>
<type>feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert</type>
<scope>()</scope>
<description>A short, imperative summary of the change</description>
<body>(optional: more detailed explanation)</body>
<footer>(optional: e.g. BREAKING CHANGE: details, or issue references)</footer>
</commit-message>Examples
<examples>
<example>feat(parser): add ability to parse arrays</example>
<example>fix(ui): correct button alignment</example>
<example>docs: update README with usage instructions</example>
<example>refactor: improve performance of data processing</example>
<example>chore: update dependencies</example>
<example>feat!: send email on registration (BREAKING CHANGE: email service required)</example>
</examples>Validation
<validation>
<type>Must be one of the allowed types. See <reference>https://www.conventionalcommits.org/en/v1.0.0/#specification</reference></type>
<scope>Optional, but recommended for clarity.</scope>
<description>Required. Use the imperative mood (e.g., "add", not "added").</description>
<body>Optional. Use for additional context.</body>
<footer>Use for breaking changes or issue references.</footer>
</validation>Final Step
<final-step>
<cmd>git commit -m "type(scope): description"</cmd>
<note>Replace with your constructed message. Include body and footer if needed.</note>
</final-step>Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.264k92.8k
Git Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.164k187kResolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.160k187k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.145k261k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.2k37k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.15.6k147FAQ
Is Conventional Commit safe to install?
skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.