agentleFS
Sign inStart free
weselbenweselben/RooForge/skills/conventional-commits/SKILL.md

conventional-commits

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Format commits per Conventional Commits v1.0.0 spec. Load when writing any commit message.

56 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use github, research and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 3 projects that use this

  • NVIDIASkill

    research

    Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.

    Also in 5 projects that use this

  • GoogleSkill

    tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

    Also in 5 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 7 projects that use this

  • SentrySkill

    skill-creator

    Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.

    Also in 5 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

  • +1 more from google

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Accidental release guard: if you don't want a release, don't use feat or fix.

    line 57

“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Conventional Commits

A lightweight convention on top of commit messages. Provides rules for explicit commit history, makes it easier to write automated tools on top of it. Dovetails with SemVer.

Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

TypeSemVerDescription
fixPATCHPatches a bug
featMINORIntroduces a feature
build—Build system / external dependencies
ci—CI config / scripts
docs—Documentation only
style—Formatting, whitespace
refactor—Code change, no bug fix, no feature
perf—Performance improvement
test—Adding/correcting tests
chore—Other, no src/test modification
revert—Reverts a previous commit

SemVer impact — every commit has one. The commit type tells CI/CD whether the next release bumps major, minor, patch, or nothing:

TypeCI/CD effectExample scenario
fixPATCH — next release is x.y.Z+1fix(auth): accept tokens with trailing whitespace
featMINOR — next release is x.Y+1.0feat(api): add user profile endpoint
feat! / fix!MAJOR — next release is X+1.0.0feat!: drop support for Node 16
BREAKING CHANGE:MAJOR — footer has same effect as !feat: allow config to extend other configs + footer
refactorNONE — no version bumpInternal cleanup, no behavior change
docsNONE — no version bumpDocumentation only
styleNONE — no version bumpWhitespace, formatting
perfNONE — no version bumpFaster but no API change
testNONE — no version bumpAdding tests only
buildNONE — no version bumpBuild system, deps
ciNONE — no version bumpCI config
choreNONE — no version bumpMisc maintenance
revertNONE — no version bumprevert: let us never speak of the noodle incident

Rule of thumb: feat and fix bump versions. Everything else is metadata — it describes the change but does not release. feat! and BREAKING CHANGE: are the only paths to major.

Accidental release guard: if you don't want a release, don't use feat or fix. If you do want a release, feat or fix is mandatory — nothing else triggers one.

Breaking Change: BREAKING CHANGE: footer or ! after type/scope introduces MAJOR version bump.

Rules

  1. Prefix: type + optional scope + optional ! + colon + space.
  2. feat for new features. fix for bug fixes.
  3. Description immediately after colon + space.
  4. Body MAY follow short description (blank line separator).
  5. Footers MAY follow body (blank line separator).
  6. Breaking changes MUST use ! in prefix or BREAKING CHANGE: footer.
  7. BREAKING CHANGE footer MUST be uppercase.

Examples

feat: send email to customer when product is shipped
feat(api)!: rename /v1/orders to /v1/checkout

feat: allow config to extend other configs
BREAKING CHANGE: `extends` key now used for config extension

revert: let us never again speak of the noodle incident
Refs: 676104e, a215868

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free