gh-auth-isolation

Managing multiple GitHub accounts in agent workflows requires isolating credentials and config directories to prevent context mixing. This Skill detects identities and switches contexts automatically, ensuring operations execute under the correct user without manual token handling.

Pushing from an EMU environment with the wrong identity happens when credential contexts overlap. Config directory isolation separates EMU and personal accounts, allowing pushes to personal repositories to execute with the correct GitHub user by default.

Creating pull requests on personal forks without switching your default login is possible through safe token extraction. The Skill retrieves the specific account token needed for the fork operation without altering the active global GitHub CLI context.

Yes, GitHub CLI is a required dependency for isolating authentication tokens. The Skill leverages the GitHub CLI framework and your existing authentication tokens to detect identities, switch contexts, and maintain secure multi-account operations.

Preventing credential mixing between EMU and personal accounts requires strict config directory isolation and automated identity detection. This approach follows security guidelines to avoid hardcoded tokens and ensures each GitHub action maintains the correct user context.

Shell aliases provide quick context switching between GitHub accounts, but limitations arise if security guidelines are not followed. Avoid hardcoded tokens and ensure complete config directory isolation to prevent unauthorized access during automated agent workflows.