flpbalada/fb-skills

conventional-commit

Draft or review Conventional Commits messages with type, optional scope, imperative summary, body, footer, and breaking-change notes.

First seen May 4, 2026

Installation

$ npx skills add flpbalada/fb-skills --skill conventional-commit

Summary

  • Draft or review Conventional Commits messages with type, optional scope, imperative summary, body, footer, and breaking-change notes.
  • Use when user asks for a commit message, commit title and body, changelog-safe wording, or commit-format review.
  • Do not use for PR descriptions; use summarize-branch.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from flpbalada/fb-skills · top by installs.

npx skills add flpbalada/fb-skills

Browse all from flpbalada/fb-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 7
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,880 B
  • docs SUMMARY.md 327 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 15 installs

SKILL.md

Conventional Commits

Write machine-readable commit messages.

Goal

Use Conventional Commits format. Make intent clear. Support automated tooling.

Format

<type>[optional scope]: <description>

[optional body]

[optional footer]

Types

  • feat: new feature.
  • fix: bug fix.
  • docs: documentation only.
  • style: formatting or code style only.
  • refactor: code change without feature or bug fix.
  • perf: performance improvement.
  • test: tests added or changed.
  • build: build system or dependency change.
  • ci: CI change.
  • chore: maintenance.
  • revert: revert previous commit.

Header Rules

  • Use imperative present tense: add, not added or adds.
  • Start description lowercase.
  • Do not end with a period.
  • Keep concise.
  • Add scope only when useful: fix(auth): remove stale token.

Body and Footer Rules

  • Use body when context matters.
  • Explain what and why.
  • Use bullets for multiple changes.
  • Wrap lines around 72 characters.
  • Use BREAKING CHANGE: ... for breaking changes.
  • Reference issues when useful: Closes #123.
feat(ui): add dark mode toggle

fix(auth): remove blocking overlay on login button

- adjust overlay z-index so it sits behind the button
- keep pointer events available for the login CTA

feat(api): migrate to REST v2 endpoints

BREAKING CHANGE: All API endpoints are now prefixed with /api/v2.

Output

## Commit Message
[message]

## Notes
- Type: [type]
- Scope: [scope or none]
- Breaking change: [yes/no]