agentleFS
ahonnahonn/dotfiles/.claude/skills/commit/SKILL.md

commit

Skill62 starsChanged 2 months agoMITView on GitHub

Create a conventional commit from staged changes.

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 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.
  • 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

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 3

    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:

    Add ! after type/scope for breaking changes (e.g., feat!: or feat(api)!:)

    line 45
  2. Distinctive:

    Write a clear, concise description

    line 56
  3. Distinctive:

    Add body details if the changes are complex

    line 57

“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

Create a Conventional Commit

I'll help you create a commit following the Conventional Commits 1.0.0 specification.

Checking current changes

!git status --short !git diff --cached --stat

Analyzing changes

Based on the changes, I'll create a commit message following this structure:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Conventional Commit Types

  • feat: A new feature (correlates with MINOR in SemVer)
  • fix: A bug fix (correlates with PATCH in SemVer)
  • docs: Documentation only changes
  • style: Changes that don't affect code meaning (white-space, formatting, etc)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding or correcting tests
  • build: Changes to build system or dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit

Breaking Changes

  • Add ! after type/scope for breaking changes (e.g., feat!: or feat(api)!:)
  • OR include BREAKING CHANGE: in the footer

Creating the commit

IMPORTANT: This command will NEVER execute git add. It only creates commits from already staged changes.

Based on the staged changes and any specific requirements in "$ARGUMENTS", I'll:

  1. Determine the appropriate commit type
  2. Identify if a scope is needed
  3. Write a clear, concise description
  4. Add body details if the changes are complex
  5. Include any necessary footers (BREAKING CHANGE, Refs, etc.)

Then execute the commit with:

git commit -m "$(cat <<'EOF'
[generated commit message here]
EOF
)"

Important: The commit message will be clean and professional, containing:

  • The conventional commit format (type, scope, description)
  • Optional body and footer as needed

The commit will follow all Conventional Commits 1.0.0 rules:

  • Type prefix is required
  • Description immediately follows colon and space
  • Body (if included) starts one blank line after description
  • Footer (if included) starts one blank line after body
  • Breaking changes are clearly indicated

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.