agentleFS
nizovtsevnvnizovtsevnv/outline-mcp-rs/.claude/skills/commit/SKILL.md

commit

Skill7 starsChanged 9 months agoMITView on GitHub

Collect uncommitted changes and create a semantic commit with a descriptive message

  • Reads credentials

187 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use act-on-feedback, generate-run-commands 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.
  • 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 4 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 4 projects that use this

  • 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

  • MindgamesSkill

    branch

    Use when a user asks to create a new local git branch and start issue work (for example, "create branch" or "start working on issue XYZ"). Use this for issue-based branch naming in the `type/scope-short-description` pattern and for always syncing local `main` from `origin/main` before creating the new branch, creating the local tracking `main` branch first when needed.

    Also in 9 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

  • 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

  • Other versions187 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 187

    1. microsoft/vscode★ 195ksame name
    2. TryGhost/Ghost★ 56ksame name
    3. ToolJet/ToolJet★ 41ksame name
    4. ShareX/ShareX★ 41ksame name
    5. openai/symphony★ 27ksame name
    6. ccusage/ccusage★ 19ksame name
    7. ryoppippi/ccusage★ 19ksame name
    8. windmill-labs/windmill★ 19ksame name
    9. EverMind-AI/EverMemOS★ 14ksame name
    10. EverMind-AI/EverOS★ 14ksame name

    177 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 167 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Run git status (without -uall) and git diff (staged + unstaged) in parallel to understand changes

    line 14
  2. Distinctive:

    Run git log --oneline -5 for recent commit context

    line 15
  3. Distinctive:

    If changes span multiple scopes — use the primary one or omit

    line 27
  4. Distinctive:

    Commit body (after blank line) explains why, not what

    line 28
  5. Distinctive:

    Commit messages in English

    line 29
  6. Very specific:

    Create the commit via HEREDOC.

    line 30
  7. Very specific:

    If a pre-commit hook fails — fix the issue, re-stage and create a new commit (never --amend)

    line 31
  8. Distinctive:

    Never commit files containing secrets

    line 36
  9. Very specific:

    Never use --no-verify or --no-gpg-sign

    line 37
  10. Distinctive:

    Never amend without explicit request

    line 38
  11. Distinctive:

    If there are no changes — report and stop

    line 39

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

Semantic Commit

Collect all uncommitted changes and create a single structured commit.

Process

  1. Run git status (without -uall) and git diff (staged + unstaged) in parallel to understand changes
  2. Run git log --oneline -5 for recent commit context
  3. Analyze changes: which files are affected, what was added/removed, purpose of the changes
  4. Stage files by name (do not use git add -A; never add .env, credentials, binary files)
  5. Compose a commit message in conventional commits format:
    • feat(scope): description — new functionality
    • fix(scope): description — bug fix
    • docs(scope): description — documentation
    • refactor(scope): description — refactoring without behavior change
    • perf(scope): description — performance improvement
    • test(scope): description — tests
    • chore(scope): description — maintenance
    • Scope = affected crate or area (app, core, db, broker, i18n)
    • If changes span multiple scopes — use the primary one or omit
    • Commit body (after blank line) explains why, not what
    • Commit messages in English
  6. Create the commit via HEREDOC. Never use --no-verify.
  7. If a pre-commit hook fails — fix the issue, re-stage and create a new commit (never --amend)
  8. Show git status after the commit to confirm

Rules

  • Never commit files containing secrets
  • Never use --no-verify or --no-gpg-sign
  • Never amend without explicit request
  • If there are no changes — report and stop
  • Summary line up to 72 characters
  • Communicate in the user's language

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.