agentleFS
Sign inStart free
ordinary9843ordinary9843/claude-gitizens/.claude/skills/git/SKILL.md

git

Skill0 starsChanged 5 months agoMITView on GitHub

Enforce conventional git commit messages for claude-gitizens plugin. Single-line format <type>: <description>. Types: feat, fix, docs, chore, system. No Co-Authored-By. No trailers.

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sql, databases and 10 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.
  • thechandanbhagatSkill

    sql

    Write SQL queries, optimize database performance, design schemas, and debug SQL issues. Use for database operations, query optimization, and schema design.

    Also in 4 projects that use this

  • mrgoonieSkill

    databases

    Work with MongoDB (document database, BSON documents, aggregation pipelines, Atlas cloud) and PostgreSQL (relational database, SQL queries, psql CLI, pgAdmin). Use when designing database schemas, writing queries and aggregations, optimizing indexes for performance, performing database migrations, configuring replication and sharding, implementing backup and restore strategies, managing database users and permissions, analyzing query performance, or administering production databases.

    Also in 3 projects that use this

  • mrgoonieSkill

    devops

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.

    Also in 4 projects that use this

  • MicrosoftSkill

    typescript

    TypeScript best practices for this monorepo. Use this skill when: (1) writing new TypeScript code, (2) reviewing TypeScript code, (3) working with API responses, fetch calls, or JSON parsing, (4) adding or modifying types and interfaces.

    Also in 4 projects that use this

  • VercelSkill

    react

    React renderer for json-render that turns JSON specs into React components. Use when working with @json-render/react, building React UIs from JSON, creating component catalogs, or rendering AI-generated specs.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    test

    Also in 8 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 51 edited versions we read keep these.

  • 1

    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:

    No vague messages — chore: update is bad, chore: update check-access script is good

    line 36
  2. Distinctive:

    Only when the "why" cannot be inferred from the type + description alone.

    line 42

“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

Git Commit Convention

Goal: Every commit must have a short, single-line message in the format <type>: <description>. The description should be lowercase, imperative, and under 72 characters. No multi-line bodies unless the change genuinely cannot be understood without one.

Format

<type>: <short description>
  • type: one of the allowed prefixes (see below)
  • description: imperative mood, lowercase, no period at end
  • length: aim for under 50 chars, hard limit 72 chars

Allowed Types

TypeWhen to use
featAdding a new skill, command, or capability
fixFixing a bug or broken behavior in a skill
docsChanges to README or skill documentation only
choreMaintenance tasks, config changes, cleanup
systemPlugin infrastructure: hooks, setup scripts, settings

Rules

  1. One commit per logical change — do not bundle unrelated changes
  2. Single line only — no body, no footer unless strictly necessary
  3. Lowercase description — feat: add propose skill not feat: Add Propose Skill
  4. Imperative mood — fix: handle missing world state not fixed or fixes
  5. No vague messages — chore: update is bad, chore: update check-access script is good
  6. No Co-Authored-By — never add this trailer
  7. No --amend on pushed commits

When a Body IS Acceptable

Only when the "why" cannot be inferred from the type + description alone.

fix: fall back to python3 base64 decode on Windows

base64 -d is not available in Git Bash on Windows; python3
decode is cross-platform and already required by the plugin.

Examples

See examples/ for good and bad examples per type:

  • examples/feat.md
  • examples/fix.md
  • examples/docs.md
  • examples/chore.md
  • examples/system.md

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