github-multi-account

Detect GitHub accounts and set up aliases for switching between personal and work profiles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the setup and management of multiple GitHub accounts, automating the process of switching between accounts and managing aliases.

Core Features & Use Cases

  • Account Detection: Automatically detects multiple GitHub accounts linked to the user's GitHub Copilot.
  • Alias Setup: Sets up account-locked GitHub aliases for personal and work accounts.
  • Command Execution: Allows users to switch between accounts using simple commands like ghp for personal and ghw for work.
  • Use Case: Ideal for developers who manage multiple GitHub accounts for personal and professional projects, enabling quick and secure account switching.

Quick Start

Use the github-multi-account skill to automatically set up GitHub aliases for your personal and work accounts.

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 for personal and work projects?

Switch multiple GitHub accounts by setting up account-locked aliases that execute `gh auth switch` commands, allowing you to toggle between personal and work profiles using simple shortcuts like `ghp` and `ghw`.

What is the best way to automate GitHub account alias setup for multiple users?

Automate GitHub account alias setup by using a script that detects linked GitHub Copilot accounts and configures locked aliases, streamlining the `gh auth status` and `gh auth switch` workflow into simple commands.

Do I need the gh CLI installed to manage multi-account GitHub aliases?

Yes, you need the `gh` CLI installed because the alias setup and account switching logic relies on `gh auth status` to detect accounts and `gh auth switch` to securely change the active profile.

How does GitHub multi-account detection work with GitHub Copilot?

Multi-account detection works by checking your GitHub Copilot configuration and `gh auth status` to identify linked personal and work accounts, then mapping them to dedicated aliases for fast switching.

Can I use custom commands to switch my GitHub account instead of typing the full auth switch syntax?

Yes, you can use custom commands like `ghp` for personal and `ghw` for work, which the script maps to the underlying `gh auth switch` commands to execute the account change securely.