agentleFS
Sign inStart free
epicsagasepicsagas/epic-harness/skills/commit/SKILL.md

commit

Skill20 starsChanged 2 months agoApache-2.0View on GitHub

Conventional Commits 1.0 generator. Stages relevant files, infers type(scope): description, never uses --no-verify.

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

Create a free account to mount
Files
SKILL.md

Commit — Conventional Commits Generator

When to Trigger

  • User wants to commit, save, or check in changes
  • User asks to commit after completing a task
  • Code changes are ready and user signals completion

Process

  1. Gather context — run in parallel:
    • git status — see what changed
    • git diff HEAD — see the actual diff
    • git log --oneline -5 — match existing commit style
  2. Determine type:
    TypeWhen
    featNew feature or capability
    fixBug fix
    refactorCode change, no behavior change
    docsDocumentation only
    testAdding or correcting tests
    buildBuild system or dependencies
    choreMaintenance task
    ciCI/CD configuration
    styleFormatting, whitespace
    perfPerformance improvement
  3. Generate message: type(scope): description
    • Lowercase type, optional scope
    • Imperative mood, no period, under 72 chars
    • Breaking changes: append ! before :
    • Body only when diff needs extra context (max 3 bullet points)
  4. Stage and commit:
    • git add <specific files> — prefer explicit files over git add -A
    • git commit -m "type(scope): description"
    • Execute automatically — no confirmation needed

Anti-Rationalization

ExcuseRebuttalWhat to do instead
"I'll just use a generic message"Generic messages make git history useless.Spend 5 seconds analyzing the diff — the type and scope are obvious from the changes.
"The user didn't specify a format"Conventional Commits is the project standard — guard will block non-CC messages anyway.Always generate CC format.
"I'll commit everything together"Unrelated changes in one commit make bisect and revert impossible.If changes span multiple concerns, suggest splitting first.

Evidence Required

  • git status checked before staging
  • Only relevant files staged (not git add -A blindly)
  • Message follows type(scope): description format
  • Type accurately reflects the change (feat ≠ fix ≠ refactor)

Red Flags

  • Vague messages: "update code", "fix stuff", "changes"
  • Wrong type: using feat for a bug fix, fix for a new feature
  • Staging unrelated files
  • Using --no-verify to bypass hooks

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