agentleFS
Sign inStart free
munvardmunvard/dockterm/.claude/skills/safe-commit/SKILL.md

safe-commit

Skill48 starsChanged 5 months agoMITView on GitHub

Stage and commit DockTerm changes safely with a clear, conventional message.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. IgorKonovalov/market-analyzer★ 2same name
    2. mauroepce/claude-workspace★ 1same name
    3. niyaznurbhasha/claude-skills★ 0same name

    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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    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. Distinctive:

    Run git status and review exactly what will be committed.

    line 8
  2. Very specific:

    Make sure npm run typecheck && npm test && npm run build pass first.

    line 10
  3. Very specific:

    Write a clear conventional message (feat:, fix:, chore:, docs:) that says what changed and why.

    line 11
  4. Very specific:

    Never force-push or rewrite shared history without explicit confirmation.

    line 13

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

Safe commit

  1. Run git status and review exactly what will be committed.
  2. Stage intentionally — don't blindly git add -A. Keep unrelated changes out.
  3. Make sure npm run typecheck && npm test && npm run build pass first.
  4. Write a clear conventional message (feat:, fix:, chore:, docs:) that says what changed and why.
  5. Never force-push or rewrite shared history without explicit confirmation; if a force push is truly needed, use --force-with-lease.

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