agentleFS
imtiazrayhanimtiazrayhan/agentscamp-library/skills/conventional-commits/SKILL.md

conventional-commits

Skill1 starsChanged 5 days agoMITView on GitHub

Generate clear Conventional Commits messages from staged changes. Use when committing code and you want a well-structured, consistent commit message.

61 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use github, grilling and 9 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

  • GoogleSkill

    grilling

    Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

    Also in 5 projects that use this

  • GoogleSkill

    domain-modeling

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

    Also in 4 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

  • 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

  • +5 more from google

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 5 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the staged diff to understand what actually changed:

    line 22
  2. Distinctive:

    If nothing is returned, stop and tell the user there are no staged changes to commit.

    line 26
  3. Distinctive:

    Check the staged file list for scope hints (directory or package names):

    line 27
  4. Very specific:

    Write the subject line: type(scope): summary

    line 42
  5. Distinctive:

    No trailing period; aim for 50 characters, hard limit 72.

    line 44
  6. Distinctive:

    If the change is non-trivial, add a blank line then a body explaining the motivation and any context the diff alone does not convey.

    line 45
  7. Very specific:

    If the change breaks compatibility, mark it: append !

    line 46
  8. Very specific:

    Add footers for issue references when relevant (e.g.

    line 47

“Common” is measured: kept by at least 6 in 10 of the 55 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

This skill inspects your staged changes and produces a commit message that follows the Conventional Commits specification. It picks the right type and scope, writes a concise imperative subject, adds a body explaining the why when the change is non-trivial, and flags breaking changes correctly — so your history stays readable and your tooling (changelogs, semantic-release) keeps working.

When to use this skill

  • You have changes staged with git add and want to commit them.
  • You want a consistent, spec-compliant message instead of free-form text.
  • You are unsure which type (feat, fix, chore, …) fits the change.
  • Your repo uses semantic versioning or automated changelog generation that depends on commit conventions.

[!NOTE] This skill only reads and commits what is already staged. Stage the exact hunks you want first (git add -p). It will not stage files for you.

Instructions

  1. Read the staged diff to understand what actually changed:
    git diff --cached
    If nothing is returned, stop and tell the user there are no staged changes to commit.
  2. Check the staged file list for scope hints (directory or package names):
    git diff --cached --name-only
  3. Choose the type from the staged changes:
    • feat — a new user-facing capability
    • fix — a bug fix
    • docs — documentation only
    • style — formatting, no logic change
    • refactor — code change that neither fixes a bug nor adds a feature
    • perf — performance improvement
    • test — adding or correcting tests
    • build / ci — build system or pipeline changes
    • chore — maintenance, deps, tooling
  4. Derive an optional scope in parentheses from the affected area (e.g. auth, api, parser). Omit it if the change is broad.
  5. Write the subject line: type(scope): summary
    • Imperative mood ("add", not "added" or "adds").
    • No trailing period; aim for 50 characters, hard limit 72.
  6. If the change is non-trivial, add a blank line then a body explaining the motivation and any context the diff alone does not convey. Wrap at ~72 columns.
  7. If the change breaks compatibility, mark it: append ! after the type/scope (e.g. feat(api)!:) and add a BREAKING CHANGE: footer describing the migration.
  8. Add footers for issue references when relevant (e.g. Refs: #123, Closes: #456).
  9. Present the proposed message to the user for confirmation, then commit:
    git commit -m "feat(parser): add support for nested arrays" \
      -m "Handles arbitrarily deep nesting by recursing on bracket pairs." \
      -m "Closes: #128"

Examples

Suppose git diff --cached --name-only shows src/auth/session.ts and the diff replaces a 1-hour token TTL with a configurable value, removing the old constant.

feat(auth)!: make session token TTL configurable

Replace the hardcoded 1-hour TTL with SESSION_TTL_SECONDS so deployments
can tune session lifetime without a rebuild. Falls back to 3600 when the
variable is unset.

BREAKING CHANGE: the SESSION_MAX_AGE constant has been removed. Set the
SESSION_TTL_SECONDS environment variable instead.

Closes: #214

Commit it:

git commit \
  -m "feat(auth)!: make session token TTL configurable" \
  -m "Replace the hardcoded 1-hour TTL with SESSION_TTL_SECONDS so deployments can tune session lifetime without a rebuild. Falls back to 3600 when the variable is unset." \
  -m "BREAKING CHANGE: the SESSION_MAX_AGE constant has been removed. Set the SESSION_TTL_SECONDS environment variable instead." \
  -m "Closes: #214"

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.