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.
In this repository153 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hermes-mobile/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-automations.mdcCursor rule
- .cursor/rules/agent-device.mdcCursor rule
- .cursor/rules/agent-harness-router.mdcCursor rule
- .cursor/rules/agent-skills-overview.mdcCursor rule
- .cursor/rules/always-agent-mode.mdcCursor rule
- .cursor/rules/callstack-agent-skills-overview.mdcCursor rule
- .cursor/rules/callstack-react-native-best-practices.mdcCursor rule
- .cursor/rules/codeql-agent-hygiene.mdcCursor rule
- .cursor/rules/decision-stack.mdcCursor rule
- .cursor/rules/expo-credit-budget.mdcCursor rule
- .cursor/rules/fleet-repo-intelligence.mdcCursor rule
- .cursor/rules/hermes-mobile-prevention-july-2026.mdcCursor rule
- .cursor/rules/hermes-mobile-real-users.mdcCursor rule
- .cursor/rules/hermes-mobile-verification.mdcCursor rule
- .cursor/rules/no-desktop-hijack.mdcCursor rule
- .cursor/rules/no-manual-handoffs.mdcCursor rule
- .cursor/rules/obsidian-teammate-collaboration.mdcCursor rule
- .cursor/rules/prefer-headless-background-ops.mdcCursor rule
- .cursor/rules/react-native-best-practices.mdcCursor rule
- public/llms.txtllms.txt
- advertise-thumbgate-github-marketplaceSkill
- agent-harness-routerSkill
- agentic-pattern-selectorSkill
- agents-judgment-calls-gateSkill
- ai-native-sdlcSkill
- android-dev-summit-26-gateSkill
- anti-babysitting-mandateSkill
- anti-babysittingSkill
- background-agent-hold-gateSkill
- browseros-agent-harnessSkill
- webmcp-agent-readinessSkill
- ci-first-failSkill
- ci-pr-monitorSkill
- cloudflare-developer-stackSkill
- cloudflare-kitesurf-browserSkill
- cloudflare-monetization-gatewaySkill
- confidence-offer-gateSkill
- content-laneSkill
- context-six-blockSkill
- context-vaultSkill
- context-weight-gateSkill
- dual-model-agentic-graphragSkill
- egm-fresh-reviewSkill
- elevenlabs-voice-agentsSkill
- emeans-quant-and-instinctSkill
- explainx-trending-honestSkill
- explainx-trending-ragSkill
- future-agi-self-healing-engineSkill
- garryslist-opportunity-trackerSkill
- gemini-decisions-hold-gateSkill
- git-at-scaleSkill
- gitbutler-fleet-automationsSkill
- gitbutler-google-ssoSkill
- gitbutler-session-absorbSkill
- git-hooks-no-huskySkill
- github-marketplace-action-publishSkill
- The first 60 shown.
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
- Very specific: line 43
Treat MCP as a substitute for npm run pr:manage / Trunk
- Very specific: line 52
NEVER dual-edit Codex tools/gitbutler-route.js
≈ “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.
Files
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.shExamples (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 MCPMUST
- Enable MCP in that clone's
.grok/config.toml/.cursor/mcp.json:command = "…/mcp_isolated.sh"(wrapper asserts safety thenbut 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 mcpagainst 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]]
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
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.

