github-multi-account

Detect multiple GitHub accounts via gh auth status and configure personal/work aliases.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill github-multi-account-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill github-multi-account-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically detects when you have multiple GitHub accounts and configures a workflow to switch between personal and work contexts without manual re-auth.

Core Features & Use Cases

  • Detects multiple gh accounts with gh auth status and prompts for personal vs work.
  • Creates persistent aliases and wrappers to switch accounts based on repository context.
  • Use Case: Developers with personal and work repos can work in the correct identity seamlessly.

Quick Start

Configure the AI to detect accounts and set up personal/work gh aliases so subsequent commands use the appropriate account automatically.

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 personal and work GitHub accounts using gh?

You can configure persistent gh aliases and wrappers that automatically route commands to your personal or work GitHub account based on repository context, eliminating manual re-authentication.

How does automatic GitHub multi-account detection work?

Multi-account detection runs 'gh auth status' to list authenticated accounts and their usernames, then prompts you to designate which profile is personal and which is work for alias routing.

Do I need PowerShell to set up multiple GitHub account aliases?

PowerShell is supported for configuring multiple GitHub account aliases, implementing profile updates, PATH adjustments, and in-session command shims to ensure automatic account routing.

What is the best way to manage multiple GitHub accounts without manual re-auth?

The best way to manage multiple GitHub accounts without manual re-auth is setting up persistent aliases and wrappers that detect repository context and apply the correct account configuration automatically.

Why does my GitHub multi-account setup require PATH adjustments?

PATH adjustments are required to ensure in-session command shims and wrappers function correctly, allowing the terminal to locate scripts that route commands to the appropriate GitHub account.

Can I use gh auth status to configure personal and work GitHub profiles?

Yes, the setup process uses 'gh auth status' to detect authenticated accounts, prompts you to classify them as personal or work, and configures persistent aliases for seamless context switching.