agentleFS
Sign inStart free
ashaychangwaniashaychangwani/imprint/.claude/skills/commit/SKILL.md

commit

Skill24 starsChanged 29 days agoMITView on GitHub

Create a conventional commit from staged changes — picks type, scope, and writes the message.

189 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

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

  • 0

    Common

    Most of the 169 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a well-formed conventional commit from the currently staged changes.

    line 15
  2. Distinctive:

    Run git diff --cached --stat to see what's staged.

    line 19
  3. Distinctive:

    Run git diff --cached to read the actual diff.

    line 21
  4. Distinctive:

    If the change spans multiple areas, omit the scope.

    line 46
  5. Distinctive:

    Run the commit using a heredoc:

    line 63

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

Commit Skill

Create a well-formed conventional commit from the currently staged changes.

Step 1 — Check staged changes

Run git diff --cached --stat to see what's staged. If nothing is staged, tell the user and stop.

Run git diff --cached to read the actual diff.

Step 2 — Determine commit type

Pick the type based on the nature of the change:

TypeWhen to use
featNew user-facing feature or capability
fixBug fix
refactorCode restructuring without behavior change
perfPerformance improvement
testAdding or updating tests
docsDocumentation only
ciCI/CD configuration
choreMaintenance, dependencies, tooling
buildBuild system or external dependency changes
styleFormatting, whitespace, linting (no logic)

Step 3 — Determine scope

Pick a scope from the file paths changed. Established scopes in this repo:

cli, probe, backend, playbook, stealth-fetch, cron, notify, utils, types, replay-backend, mcp, record, redact, session-writer

If the change spans multiple areas, omit the scope. If it's a new area, derive the scope from the directory name.

Step 4 — Write the commit message

Format: <type>(<scope>): <subject>

Rules:

  • Subject line: imperative mood, lowercase, no period, under 72 chars
  • Body (optional): explain WHY, not WHAT. Wrap at 100 chars.
  • Footer (optional): BREAKING CHANGE: <description> if applicable

Step 5 — Show and confirm

Show the proposed commit message to the user. Ask if they want to proceed, edit, or cancel.

Step 6 — Execute

Run the commit using a heredoc:

git commit -m "$(cat <<'EOF'
<commit message here>
EOF
)"

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