agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/git-at-scale/SKILL.md

git-at-scale

Skill3 starsChanged 3 days agoMITView on GitHub

Client-side Git scale hygiene stolen from Cursor Continuity ("Git at any scale"): multi-pack-index, commit-graph, geometric repack, safe agent worktree GC, tip-consistency checks. NOT Origin/WAL hosting. Trigger: packs high, worktree sprawl, slow git, Cursor Continuity blog, git at any scale. Slash: /git-at-scale.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Treat mss=UNKNOWN / eventual tip as fine for CI truth

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 at scale (client steal)

Cursor Continuity/Origin is server hosting. We stay on GitHub. Steal only:

  1. Packfile proliferation → multi-pack-index + commit-graph (+ optional geometric repack)
  2. Agent throwaway worktrees → cattle under /tmp/agent-git-worktrees (clean prune only)
  3. Consistent tip for CI → --tip-consistency vs origin/<branch>
node tools/git-at-scale-engine.js --scorecard
node tools/git-at-scale-engine.js --maintenance          # cheap indexes
node tools/git-at-scale-engine.js --maintenance --geometric
node tools/git-at-scale-engine.js --prune-worktrees --base /tmp/agent-git-worktrees --dry-run
node tools/git-at-scale-engine.js --tip-consistency --branch main
npm test --silent -- tests/test-git-at-scale-engine.js  # or: node tests/test-git-at-scale-engine.js

Never

  • Rebuild S3 WAL / Origin
  • Force-prune dirty or open-PR worktrees outside the agent base
  • Treat mss=UNKNOWN / eventual tip as fine for CI truth

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.