github-multi-account

Configure GitHub personal and work aliases with ghp and ghw wrappers.

2|1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/PlagueHO/plagueho.learn --skill github-multi-account-plagueho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/PlagueHO/plagueho.learn/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/PlagueHO/plagueho.learn --skill github-multi-account-plagueho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically configure GitHub personal/work aliases for users with multiple accounts to keep workflows isolated and reduce context switching.

Core Features & Use Cases

  • Detect multiple GitHub accounts using gh auth status.
  • Prompt the user to designate personal vs work and install aliases and wrappers across the shell profile and PATH.
  • Provide stable personal/work workflows with ghp/ghw wrappers and verification steps.

Quick Start

Detect multiple GitHub accounts, identify which is personal and which is work, and let me set up the aliases and wrappers 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 manage multiple GitHub accounts with gh-cli?

To manage multiple GitHub accounts with gh-cli, you can use wrapper scripts installed across your shell profile and PATH. This allows you to configure personal and work aliases, isolating workflows and reducing context switching.

What is the best way to set up personal and work GitHub aliases?

Setting up personal and work GitHub aliases involves detecting multiple authenticated accounts and modifying your shell profile to create ghp and ghw wrappers. This automatically switches contexts to keep your workflows isolated.

Do I need PowerShell to configure multiple GitHub aliases?

Yes, you need PowerShell and gh-cli installed to configure multiple GitHub aliases. The setup detects multiple authenticated accounts via gh auth status and then installs the necessary wrapper scripts and profile modifications.

How does gh auth status detect multiple accounts for alias setup?

The gh auth status command detects multiple authenticated accounts to initiate the alias setup. It prompts you to identify which account is personal versus work, then applies the corresponding wrappers and PATH updates.

How do I verify my GitHub aliases are switching accounts correctly?

You verify GitHub aliases are switching accounts correctly by running gh api after switching contexts. This confirms the active account matches the designated ghp or ghw wrapper you executed in your shell.

Why modify the shell profile for GitHub multi-account automation?

Modifying the shell profile for GitHub multi-account automation ensures the ghp and ghw wrappers are always available in your PATH. This provides stable, isolated workflows without manually re-authenticating for each session.