github-multi-account

Detect multiple GitHub accounts via gh auth status and configure context-switching aliases.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill github-multi-account-lbouriez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill github-multi-account-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple GitHub identities manually is error-prone and time-consuming when switching between personal and work accounts.

Core Features & Use Cases

  • Detects multiple GitHub accounts via gh auth status and reports them to the user.
  • Prompts the user to label each account as personal or work and configures context-aware aliases.
  • Creates shell wrappers and gh aliases to ensure all repo operations use the correct account.
  • Use Case: A developer with personal and company repos can seamlessly push and pull using the right identity without manual switching.

Quick Start

Run the skill to detect accounts, then indicate which username is personal and which is work to complete the setup 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 on the same machine?

Managing multiple GitHub accounts involves configuring context-aware aliases and shell wrappers. This Skill detects authenticated accounts via gh auth status and automates the creation of aliases to switch contexts seamlessly.

How do I switch between personal and work GitHub accounts automatically?

You can switch automatically by labeling your accounts as personal or work. The setup applies automated shell wrappers and gh aliases, ensuring all subsequent repository operations use the correct identity.

Does this multi-account GitHub setup work with PowerShell?

Yes, the setup works with PowerShell and other shells by creating verified shell wrappers. These wrappers ensure that all subsequent gh operations route through the appropriate account alias.

What is the best way to prevent git push errors with the wrong GitHub identity?

The best way to prevent identity errors is using automated shell wrappers. This Skill configures verified wrappers and aliases that ensure all push and pull operations execute under the correct account context.

Do I need to manually authenticate each GitHub account before setup?

Yes, accounts must be authenticated via gh auth status before setup. The Skill detects present accounts, prompts you to label them as personal or work, and then applies the automated alias configuration.