agentleFS
braincandy-parallelbraincandy-parallel/tamarindos-workflow-kit/skills/git-safe/SKILL.md

git-safe

Skill0 starsChanged 55 days agoNo licenceView on GitHub

Mandatory safety protocol for all git operations — pull, push, merge, commit, checkout, branch creation, and multi-repo coordination. MUST be consulted before ANY git operation that modifies repository state, especially when working across multiple repos, deploying to VPS, dispatching agents to write code, or doing merge/rebase operations. Also trigger when you see dirty working trees, merge conflicts, untracked files blocking operations, worktree agents, parallel git operations across repos, or any git error. This skill prevents the recurring issues of lost work from worktree cleanup, cascading failures from parallel git ops, dirty trees blocking merges, deleted files that shouldn't have been deleted, and branches that never reach remotes. If you are about to run ANY git command beyond `git status` or `git log`, consult this skill first.

  • Deletes or force-pushes
  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

40 rules. About 0 are common, 28 are distinctive, and 12 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈28

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 12

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

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.