Development
github-outside-sandbox
Run Git and GitHub CLI commands through the host context when sandboxing blocks Keychain authentication, network access, or .git writes. Use for gh auth, repository or PR operations, and git index.lock or permission failures. Handles execution context only, not GitHub workflow design.
davidondrej · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add davidondrej/skills --skill github-outside-sandboxAbout this skill
name: github-outside-sandbox description: Run Git and GitHub CLI commands through the host context when sandboxing blocks Keychain authentication, network access, or .git writes. Use for gh auth, repository or PR operations, and git index.lock or permission failures. Handles execution context only, not GitHub workflow design.
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.