agentleFS
pablonificationpablonification/grok-build-consult-claude/skills/conventional-commits/SKILL.md

conventional-commits

Skill0 starsChanged 5 months agoMITView on GitHub

Write git commit messages using Conventional Commits v1.0.0. Invoke when committing, staging for commit, amending, rebasing commit messages, or when the user asks for feat:/fix:/docs: format. Do NOT load for unrelated coding tasks.

61 other projects use a version of this.

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

6 rules. 0 are common, 5 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use Conventional Commits v1.0.0 for every git commit you create.

    line 13
  2. Distinctive:

    No trailing period on the subject line

    line 42
  3. Distinctive:

    Write subject that states what changed, not how you feel about it

    line 60
  4. Distinctive:

    Add body only if context helps future readers

    line 61
  5. Very specific:

    Run git commit -m "type(scope): subject" or heredoc for body

    line 62
  6. Distinctive:

    When amending or rebasing, rewrite messages to match this format.

    line 64

“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

Conventional Commits

Use Conventional Commits v1.0.0 for every git commit you create.

Format

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Types

TypeUse for
featNew feature or capability
fixBug fix
docsDocumentation only
styleFormatting, no logic change
refactorRestructure without feat/fix
perfPerformance improvement
testTests
choreBuild, deps, tooling
ciCI/CD changes

Rules

  • Imperative mood: add handler not added handler
  • No trailing period on the subject line
  • Subject ≤ 72 characters
  • Scope when helpful: fix(consult):, feat(auth):
  • Breaking changes: footer BREAKING CHANGE: <description>

Examples

feat: add consult-claude skill
fix(consult): block Bash via allow-list tools
docs: add install instructions to README
chore: bump dependency

Workflow

  1. Review staged changes (git diff --cached or git status)
  2. Pick type and optional scope from the diff
  3. Write subject that states what changed, not how you feel about it
  4. Add body only if context helps future readers
  5. Run git commit -m "type(scope): subject" or heredoc for body

When amending or rebasing, rewrite messages to match this format.

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.