github-multi-account

To switch GitHub accounts, this Skill detects your authenticated identities via `gh auth status`, asks you to label them as personal or work, and creates `ghp` and `ghw` command aliases that automatically switch the authentication context before running commands.

Yes, you can create command-line aliases to switch GitHub accounts. This Skill generates `gh-personal` and `gh-work` wrappers that execute `gh auth switch --user`, adding them to your PowerShell profile and PATH so your commands always target the correct identity.

The best way to manage multiple GitHub accounts is by pairing detected identities with dedicated aliases. This Skill enforces usage rules to prevent manual switching errors, guiding you to bind specific repository operations to either your personal or employer account.

No, you do not need to manually run `gh auth switch`. This Skill replaces manual switching with `ghp` and `ghw` wrapper aliases that enforce context safety, preventing bare `gh` repository operations and ensuring commands target the correct authenticated user.

Your GitHub CLI commands run under the wrong account context because bare `gh` repo ops lack identity binding. This Skill verifies your resulting logins and provides safety guidance to bind repository operations to the correct personal or work account.

Yes, this multi-account GitHub setup works with PowerShell profiles. The Skill adds the generated `ghp` and `ghw` wrappers directly to your PowerShell profile and PATH, ensuring the authenticated command aliases are available across your developer tooling sessions.