What problem does it solve? Developers with multiple GitHub accounts (personal and work/EMU) often run gh CLI commands under the wrong identity, causing commits, PRs, and repo operations to be attributed to the wrong account. This Skill detects the signed-in accounts and sets up account-locked aliases so every command targets the correct identity. ## Core Features & Use Cases - Account Detection: Runs gh auth status to list all authenticated GitHub accounts and asks the user which is personal and which is work. - Automated Alias Setup: Writes gh-personal/gh-work PowerShell functions into the user profile, creates ghp.cmd/ghw.cmd wrappers in a bin directory, and adds that directory to the user PATH. - Verification & Enforcement: Verifies each alias with gh api user and enforces usage rules so repo operations always use the correct account-bound alias. - Use Case: A developer who contributes to open source with a personal account and to employer repos with a work account can run ghp for personal repos and ghw for work repos without ever manually switching auth. ## Quick Start Ask the assistant to detect my GitHub accounts and set up the ghp and ghw aliases for my personal and work accounts.