How do I install the Commit Style skill?

Run npx skillmds@latest add tibsfox/commit-style in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Commit Style safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Commit Style?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Commit Style free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Commit Style?

Tibsfox (@tibsfox) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Commit Style by tibsfox — Agent Skill

Name: Commit Style
Rating: 4.2 (5 reviews)
Author: Tibsfox

File contents

Commit Style — Conventional Commits

Generates commit messages following the Conventional Commits / Angular convention for clear, consistent version history.

Format

<type>(<scope>): <subject>

[optional body]

[optional footer]

Types

Type	Use
`feat`	New feature
`fix`	Bug fix
`docs`	Documentation only changes
`style`	Formatting, whitespace, no logic change
`refactor`	Neither fix nor feature
`perf`	Performance improvement
`test`	Adding or updating tests
`build`	Build system or external dependencies
`ci`	CI/CD configuration changes
`chore`	Other maintenance tasks
`revert`	Reverting a previous commit

Rules

Subject: ≤72 chars (50 preferred), lowercase, imperative mood, no trailing period.
Imperative test: "If applied, this commit will [subject]".
Scope: Specific module/component in lowercase — e.g. feat(auth), fix(api), docs(readme), refactor(core).
Body: Optional. Explain WHY/WHAT, not HOW. Wrap at 72 chars. Blank line between subject and body.
Footer: Optional. BREAKING CHANGE: …, Closes #N, Co-Authored-By: … (HUMAN co-authors only — Co-Authored-By: Claude … trailers are hard-blocked by .claude/hooks/validate-commit.cjs, v1.49.621 policy).

Atomic Commits

One logical change per commit. Split unrelated changes into separate commits — this makes surgical rollback and git bisect possible.

Examples

Simple feature:

feat(auth): add password reset functionality

Bug fix with issue reference:

fix(api): handle null response from user endpoint

The /users/:id endpoint could return null for deleted users,
causing a crash in the profile component.

Closes #456

Breaking change:

feat(api): change authentication to JWT

Migrate from session-based auth to JWT tokens for better
scalability and stateless operation.

BREAKING CHANGE: All API clients must now include JWT token
in Authorization header. Session cookies no longer accepted.

Documentation update:

docs(readme): update installation instructions

Add troubleshooting section for common npm issues
and clarify Node.js version requirements.

Anti-Patterns

Vague subjects: "fix bug", "update stuff"
Past/present tense: "added", "adds" — use the imperative "add"
Multiple changes in one commit: "add login and fix navbar"
Implementation trivia: "change line 47"
Emotional language: "finally fixed!!!"

---name: commit-styledescription: Crafts and generates professional conventional commit messages following Angular/Conventional Commits format. Use when committing changes, writing git commit messages, or when user mentions commit message.---# Commit Style — Conventional CommitsGenerates commit messages following the Conventional Commits / Angular convention for clear, consistent version history.## Format```<type>(<scope>): <subject>[optional body][optional footer]```## Types| Type | Use ||------|-----|| `feat` | New feature || `fix` | Bug fix || `docs` | Documentation only changes || `style` | Formatting, whitespace, no logic change || `refactor` | Neither fix nor feature || `perf` | Performance improvement || `test` | Adding or updating tests || `build` | Build system or external dependencies || `ci` | CI/CD configuration changes || `chore` | Other maintenance tasks || `revert` | Reverting a previous commit |## Rules- **Subject:** ≤72 chars (50 preferred), lowercase, imperative mood, no trailing period.- **Imperative test:** "If applied, this commit will _[subject]_".- **Scope:** Specific module/component in lowercase — e.g. `feat(auth)`, `fix(api)`, `docs(readme)`, `refactor(core)`.- **Body:** Optional. Explain WHY/WHAT, not HOW. Wrap at 72 chars. Blank line between subject and body.- **Footer:** Optional. `BREAKING CHANGE: …`, `Closes #N`, `Co-Authored-By: …` (HUMAN co-authors only — `Co-Authored-By: Claude …` trailers are hard-blocked by `.claude/hooks/validate-commit.cjs`, v1.49.621 policy).## Atomic CommitsOne logical change per commit. Split unrelated changes into separate commits — this makes surgical rollback and `git bisect` possible.## ExamplesSimple feature:```feat(auth): add password reset functionality```Bug fix with issue reference:```fix(api): handle null response from user endpointThe /users/:id endpoint could return null for deleted users,causing a crash in the profile component.Closes #456```Breaking change:```feat(api): change authentication to JWTMigrate from session-based auth to JWT tokens for betterscalability and stateless operation.BREAKING CHANGE: All API clients must now include JWT tokenin Authorization header. Session cookies no longer accepted.```Documentation update:```docs(readme): update installation instructionsAdd troubleshooting section for common npm issuesand clarify Node.js version requirements.```## Anti-Patterns- Vague subjects: "fix bug", "update stuff"- Past/present tense: "added", "adds" — use the imperative "add"- Multiple changes in one commit: "add login and fix navbar"- Implementation trivia: "change line 47"- Emotional language: "finally fixed!!!"

Frequently asked questions

Commit Style