agentleFS
Sign inStart free
nb-99nb-99/skillektion/skills/git-working-agreement/SKILL.md

git-working-agreement

Skill1 starsChanged 3 months agoMITView on GitHub

When making changes to a repository, use this skill.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

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

    Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work.

    line 13
  2. Distinctive:

    Prefer fast-forward/rebase merges.

    line 17
  3. Very specific:

    Update a feature branch by rebasing it onto its base branch rather than merging the base branch into it.

    line 18
  4. Very specific:

    Use git cli commands to interact with repositories.

    line 19
  5. Distinctive:

    Follow the hosting workflow's authorization rules for comments, reviews, and other pull-request or issue writes.

    line 20

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Git Working Agreement

  • Make changes on worktrees, or alternatively a feature branch. Never on main unless specified or asked to.
  • Branch and worktree names should be descriptive and use proper prefixes.
  • An explicit user request that names the repository or branch and a bounded Git write action authorizes that action. Otherwise, show the exact command or change and ask for confirmation.
  • Always confirm immediately before destructive, irreversible, privilege-changing, or materially broader work. This includes deleting branches or tags, discarding changes, rewriting published history, force pushing, changing access, and writes outside the requested scope.
  • Prefer fast-forward/rebase merges; create a merge commit only when fast-forward/rebase is impossible or explicitly requested.
  • Update a feature branch by rebasing it onto its base branch rather than merging the base branch into it; when it is behind origin/main, fetch and rebase onto origin/main rather than using a merge-based pull.
  • Use git cli commands to interact with repositories; gh for GitHub, glab for GitLab.
  • Follow the hosting workflow's authorization rules for comments, reviews, and other pull-request or issue writes. When no hosting workflow is loaded, show the exact mutation and confirm before running it.
  • For commit messages, use the git-conventional-commits skill.

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