github-multi-account

Detect multiple GitHub accounts and configure gh aliases for personal and work contexts.

9|1|Updated Jul 21, 2025

Search Tags:#automation #devops #github #cli #aliases #accounts #multi-account

Ready to run

npx skills add https://github.com/usepowershell/PoshMcp --skill github-multi-account-usepowershell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill github-multi-account-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and configure account-specific gh aliases to enable seamless GitHub usage across multiple accounts during AI-assisted workflows.

Core Features & Use Cases

Detect multiple GitHub accounts using gh auth status and identify personal vs work accounts.
Create and expose alias wrappers (e.g., gh-personal and gh-work) to switch contexts safely.
Update user profile, PATH, and available wrappers automatically to enforce correct account usage during automation.
Use Case: An AI agent executes repository operations and always uses the correct account based on the target repo owner.

Quick Start

Run the skill to detect multiple GitHub accounts and automatically configure personal/work aliases.

Frequently Asked Questions about github-multi-account

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I switch between multiple GitHub accounts when using an AI agent?▼

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.

What is the best way to manage personal and work GitHub accounts in automated development?▼

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.

Do I need the GitHub CLI installed to configure multiple account aliases?▼

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.

How does multi-account GitHub configuration handle PATH and profile updates?▼

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.

Can I use this skill to separate GitHub contexts for different repository owners?▼

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.

Why does my AI assistant struggle with GitHub operations across different accounts?▼

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.