Github Outside Sandbox
Run Git and GitHub CLI commands on the host when sandboxing blocks Keychain auth...
Install
npx skills add davidondrej/skills --skill github-outside-sandbox -g -a claude-code -y- Repository
- davidondrej/skills4.2k
- Category
- Git and review
- Updated
- 3d ago
- License
- MIT
- Context cost
- Lightabout 264 tokens
- Runs scripts
- No, instructions only
What it does
Run Git and GitHub CLI commands on the host when sandboxing blocks Keychain auth, network access, or .git writes. Use for gh auth, repo/PR operations, index.lock, or permission errors; covers execution context only.
GitHub Outside Sandbox
- Start normally. Escalate only the blocked command and only within the user's authorization.
- If sandboxed
gh auth statusfails, rerun it outside the sandbox before claiming authentication is broken. Never expose or copy tokens. - Run GitHub CLI network operations outside the sandbox when required:
gh repo ...,gh pr ..., and relatedghcommands. - Run Git writes outside the sandbox when
.gitis outside writable roots or errors mentionindex.lockorOperation not permitted:git add,git commit, andgit push. - Use the harness's official host-execution mechanism. In Codex, set
sandbox_permissions: "require_escalated", give a concretejustification, and use only a narrow safeprefix_rulewhen appropriate. - Never use shell wrappers, credential copying, or broad approval prefixes to bypass the sandbox.
- Verify from the host context with
git status -sb,git remote -v, and the relevantgh ... viewcommand. Ask the user to authenticate only if the host-context check also fails.
