github-multi-account

To switch between multiple GitHub accounts for AI workflows, this skill detects your authenticated accounts via the GitHub CLI and configures safe profile changes. It sets up alias wrappers like gh-personal and gh-work to ensure automation uses the correct context.

Managing personal and work GitHub accounts in automated development is best done by creating distinct CLI alias wrappers. This skill detects your accounts, prompts for personal vs work categorization, and exposes dedicated wrappers to enforce correct account usage.

Yes, you need the GitHub CLI installed to configure multiple account aliases. The skill relies on the gh auth status command to detect existing accounts and subsequently guides the AI to set up the necessary profile and PATH modifications.

Multi-account GitHub configuration handles PATH and profile updates by automatically applying modifications when aliases are set. This ensures the newly created wrappers are correctly exposed and prioritized during AI-assisted repository operations.

Yes, you can use this skill to separate GitHub contexts for different repository owners. It configures account-specific aliases that allow an AI agent to execute repository operations and automatically select the correct authenticated account based on the target repo owner.

Your AI assistant struggles with GitHub operations across different accounts because it lacks distinct context boundaries. This skill resolves the issue by detecting multiple accounts and generating safe alias wrappers to prevent accidental cross-account commits.