agentleFS
IgorGanapolskyIgorGanapolsky/mac-yolo-safeguards/.agents/skills/gitbutler-mcp-isolated/SKILL.md

gitbutler-mcp-isolated

Skill3 starsChanged 4 days agoMITView on GitHub

GitButler MCP (`but mcp serve`) only on an isolated clone that already passed assert_but_setup_safe.sh. Never add it to global ~/.grok/config.toml (mac-yolo/ThumbGate cwd would expose but tools on a shared tree). Trigger: GitButler MCP, but mcp, gitbutler mcp.json. Slash: /gitbutler-mcp-isolated.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

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

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

    Treat MCP as a substitute for npm run pr:manage / Trunk

    line 43
  2. Very specific:

    NEVER dual-edit Codex tools/gitbutler-route.js

    line 52

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

GitButler MCP — isolated clone only

but mcp serve exposes workspace/review tools. That is GitButler workspace mode. Shared primaries (ThumbGate, mac-yolo 83 worktrees, RealEstate) stay on gh + GitHub MCP.

bash ~/.grok/skills/gitbutler-fleet-safe/scripts/assert_but_setup_safe.sh "$PWD"
# exit 0 only on a single-owner clone with one worktree
.agents/skills/gitbutler-fleet-automations/scripts/mcp_isolated.sh

Examples (show, don't tell)

Weak: Add GitButler MCP globally so every agent can use it.

Gold:

$ bash .agents/skills/gitbutler-fleet-automations/scripts/mcp_isolated.sh
gitbutler-mcp-isolated: setup guard refused — use gh/GitHub MCP

MUST

  • Enable MCP in that clone's .grok/config.toml / .cursor/mcp.json: command = "…/mcp_isolated.sh" (wrapper asserts safety then but mcp serve).
  • Workspace tools prefer filesystem roots the MCP client supplies.

NEVER

  • [mcp_servers.gitbutler] in ~/.grok/config.toml (global Grok cwd is shared repos)
  • claude mcp add gitbutler but mcp against ThumbGate / mac-yolo / RealEstate primary
  • Treat MCP as a substitute for npm run pr:manage / Trunk
  • Dual-edit Codex tools/gitbutler-route.js

Rubric

  • mcp_isolated.sh on this linked worktree → non-zero, message contains refused/REFUSE
  • no [mcp_servers.gitbutler] in ~/.grok/config.toml
  • doctor_exit=0 on fleet automations doctor
  • evidence: test-gitbutler-fleet-automations PASS
  • NEVER dual-edit Codex tools/gitbutler-route.js

Related

  • [[gitbutler-fleet-automations]]
  • [[gitbutler-fleet-safe]]

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.