agentleFS
Sign inStart free
enkr1enkr1/claude-code-skills/skills/commit/SKILL.md

commit

Skill1 starsChanged 23 days agoMITView on GitHub

Use when committing code changes — enforces gitmoji + conventional commit format with anti-AI-signature rules for human-looking commits

188 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use validate-plan, act-on-feedback 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.
  • shawn-dumasSkill

    validate-plan

    Validate an orchestration plan after pre-flight certification. Runs adversarial review, deep review (verify prompt data against codebase), and PoC gate for risky approaches. Auto-invoked by orchestrate-* skills at Step 8.

    Also in 5 projects that use this

  • MicrosoftSkill

    act-on-feedback

    Act on user feedback attached to the current session. Use when the user submits feedback on the session's changes via the Submit Feedback button.

    Also in 3 projects that use this

  • decocmsSkill

    add-mcp-tools

    Guide for adding new MCP tools with consistent patterns for schemas, tool definitions, registry updates, and Better Auth integration

    Also in 3 projects that use this

  • MicrosoftSkill

    generate-run-commands

    Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.

    Also in 3 projects that use this

  • mitsuhikoSkill

    oebb-scotty

    Austrian rail travel planner (ÖBB Scotty). Use when planning train journeys in Austria, checking departures/arrivals at stations, or looking for service disruptions. Covers ÖBB trains, S-Bahn, regional trains, and connections to neighboring countries.

    Also in 3 projects that use this

  • mitsuhikoSkill

    pi-share

    Load and parse session transcripts from shittycodingagent.ai/buildwithpi.ai/buildwithpi.com/pi.dev (pi-share) URLs. Fetches gists, decodes embedded session data, and extracts conversation history.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use imperative mood ("add", "fix", "prevent", not "added", "fixed")

    line 41
  2. Very specific:

    NEVER add Co-Authored-By lines

    line 68
  3. Very specific:

    NEVER add Generated with Claude Code or similar

    line 69
  4. Distinctive:

    NEVER start with "This commit..." or "This change..."

    line 71
  5. Distinctive:

    NEVER add bullet-point lists in commit body

    line 72
  6. Distinctive:

    Keep it short, casual, imperfect.

    line 73

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

Format

<emoji> <type>(<scope>): <comprehensive description>

Single line. No body unless explicitly needed for breaking changes.

Emoji → Type Mapping

EmojiTypeWhen to Use
✨featNew feature or capability
🐛fixBug fix
♻️refactorCode restructure without behavior change
📝docsDocumentation only
✅testAdding or updating tests
⚡️perfPerformance improvement
🎨styleCode formatting, no logic change
🔧choreConfig, dependencies, tooling
🔥removeRemoving code or files
🚀deployDeployment related
⏪️revertReverting changes

Scopes

Derive from the changed files — directory name, feature area, or module. Omit for project-wide changes.

Description Guidelines

Be comprehensive in one line:

  • State WHAT changed AND WHY if non-obvious
  • Use imperative mood ("add", "fix", "prevent", not "added", "fixed")
  • Include the user impact when relevant

Good:

✨ feat(auth): add OAuth2 PKCE flow for mobile clients
🐛 fix(api): prevent race condition on concurrent profile updates (#163)
♻️ refactor(ui): CSS-first approach for card and form components

Bad:

fix: bug fix                     # Too vague
✨ feat: added new feature       # Past tense, no scope, no description
🐛 fix(ui): fix issue            # Redundant, no actual description

PR References

Append issue/PR number when closing or referencing:

🐛 fix(api): preserve metadata field when updating resource name (#151)

Must Look Human

  • NEVER add Co-Authored-By lines
  • NEVER add Generated with Claude Code or similar
  • NEVER use 🤖 emoji
  • NEVER start with "This commit..." or "This change..."
  • NEVER add bullet-point lists in commit body
  • Keep it short, casual, imperfect. One line when possible.

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.

Reviews can't be read right now.

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