agentleFS
mrveissmrveiss/AutoBot-AI/.claude/skills/commit/SKILL.md

commit

Skill39 starsChanged 18 days agoApache-2.0View on GitHub

Standardized commit workflow with pre-flight checks, auto-format, and retry logic for pre-commit hooks

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

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

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 0

    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. Very specific:

    If on release or main directly: STOP and ask user.

    line 19
  2. Very specific:

    If unrecognized files appear staged: git restore --staged <file>

    line 51

“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

Commit Workflow

Self-healing commit sequence that formats, stages, commits, and verifies — retrying up to 3x on hook failures.

Step 1 — Pre-flight state check

git branch --show-current        # Must NOT be release/main directly
git status                       # Identify all modified/untracked files
git diff --staged --name-only    # What's already staged?
git stash list                   # Warn if stashes exist

If on release or main directly: STOP and ask user.

Step 2 — Auto-format Python files

For every .py file that will be committed:

BLACK=$HOME/.cache/pre-commit/repoefsi1klb/py_env-python3/bin/black

for FILE in $(git diff --staged --name-only | grep '\.py$'); do
    $BLACK --line-length=88 "$FILE"
    isort --profile=black --line-length=88 "$FILE"
    git add "$FILE"    # Re-stage after formatting
done

Skip if no .py files are being committed.

Step 3 — Stage files

Stage only files relevant to the current issue. Never git add . blindly.

git add <file1> <file2> ...   # Preferred: explicit files
# OR
git add -u                     # All tracked modifications (safe if worktree is clean)

# Verify:
git diff --staged --name-only
git diff --staged --stat

If unrecognized files appear staged: git restore --staged <file>

Step 4 — Commit with retry loop

Attempt up to 3 times, fixing hook failures between attempts:

for ATTEMPT in 1 2 3; do
    echo "Commit attempt $ATTEMPT/3..."

    git commit -m "$(cat <<'MSG'
<type>(scope): <description> (#issue-number)
MSG
)" && echo "✅ Committed on attempt $ATTEMPT" && break

    # Hook failed — re-stage any files hooks modified
    echo "⚠️  Hook failed. Re-staging modified files..."
    git add -u
done

NEVER use --no-verify. Fix the underlying issue.

Step 5 — Post-commit verification

git log -1 --stat        # Verify commit landed
git diff                 # Nothing left uncommitted
git diff --staged        # Nothing accidentally staged

Step 6 — Report

State commit hash, files changed, branch, and whether more commits are needed.

Commit Message Format

<type>(scope): <description> (#issue-number)

Types: feat · fix · refactor · test · docs · chore · perf

Common Hook Failures & Fixes

HookSymptomFix
black"reformatted X.py"git add -u and retry
isort"Imports are incorrectly sorted"isort --profile=black <file> && git add <file>
flake8"E501 line too long"Shorten the line, git add <file>
autoflakeremoved unused importAccept it, git add -u
warn-untracked-filesuntracked source files detectedRun git diff --cached --name-only, verify staged files belong on this branch

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.