gh-auth-isolation

Safely isolate multiple GitHub identities by configuring a dedicated GH_CONFIG_DIR directory for each account. This approach extracts per-account tokens and sets environment variables to prevent credential leakage and misattributed actions across automated agent workflows.

The gh auth status command detects the active GitHub identity by checking the current authentication state. This identity detection mechanism ensures automated agents operate under the correct EMU work account or personal account before executing any GitHub operations.

Yes, you can switch between EMU work accounts and personal GitHub accounts in CI environments. The Skill provides shell aliases and environment-variable helpers to switch contexts safely without persisting credentials, ensuring safe context switching in shells, scripts, and CI.

The best way to prevent unintended cross-account actions with the GitHub CLI is to use per-account configuration directories and guardrails against mixing accounts. This isolates GitHub identities across agents and prevents misattributed actions in your workflows.

Yes, separate token management is required for GitHub identity isolation in scripts. The Skill extracts per-account tokens and uses dedicated configuration directories to ensure safe context switching without persisting credentials across your automated workflows.