github-multi-account

Detect GitHub accounts with gh auth status and configure shell wrappers for automatic switching.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill github-multi-account-carlossardo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill github-multi-account-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and configure GitHub aliases for multi-account setups, enabling seamless switching between personal and work accounts without manual re-auth switching.

Core Features & Use Cases

  • Detect multiple accounts using gh auth status.
  • Prompt the user to map personal vs work accounts.
  • Create shell/PowerShell wrappers and profile updates to switch accounts automatically.
  • Enforce usage of aliases for repository operations to avoid mixing accounts.

Quick Start

Detect accounts with gh auth status, ask the user which is personal or work, then apply aliases and wrappers to enable seamless switching.

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 automatically?

To switch GitHub accounts automatically, this tool detects your active accounts using gh auth status and writes shell profile wrappers and aliases to enable seamless switching without manual re-authentication.

What is the best way to manage multiple GitHub accounts in my terminal workflows?

Managing multiple GitHub accounts involves mapping personal and work profiles to specific aliases, then applying shell wrappers and PATH updates to enforce account separation and prevent mixing identities across projects.

How do I configure git aliases for a multi-account GitHub setup?

Configuring git aliases for multi-account setups requires verifying your accounts with gh auth status, mapping them to personal or work, and applying the generated profile functions to automate switching.

Does this multi-account switching work with both shell and PowerShell environments?

Yes, multi-account switching supports both shell and PowerShell environments by generating specific wrappers and profile updates tailored to your system to ensure safe account separation.

Why do I need to use aliases for repository operations across multiple GitHub accounts?

Using aliases for repository operations is necessary to enforce workflow separation and prevent accidentally mixing personal and work account credentials when pushing code or managing repositories.

What do I need to set up before configuring multi-account GitHub aliases?

Before configuring multi-account GitHub aliases, you need two or more active GitHub accounts and the gh auth status command available to verify them, ensuring seamless switching across your projects.