github-multi-account

Configure GitHub CLI authentication switching with shell aliases and wrappers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing multiple GitHub accounts on a single machine often leads to authentication conflicts and manual overhead when switching between personal and work identities.

Core Features & Use Cases

  • Automated Alias Setup: Automatically configures PowerShell profiles and CMD wrappers to handle account switching.
  • Context-Aware Operations: Provides dedicated aliases (ghp/ghw) to ensure the correct GitHub identity is used for specific repositories.
  • Use Case: If you frequently switch between a personal GitHub account for open-source projects and a corporate account for work, this skill automates the authentication context so you never accidentally push to the wrong account.

Quick Start

Ask the agent to set up my multi-account GitHub aliases using the github-multi-account skill.

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 on the same machine?

To switch between multiple GitHub accounts, this Skill configures PowerShell profiles and CMD wrappers to create dedicated aliases like 'ghp' and 'ghw'. This ensures the correct GitHub identity is used for specific repositories, preventing accidental pushes to the wrong account.

Do I need the GitHub CLI installed to automate authentication switching?

Yes, the GitHub CLI ('gh') is required to automate authentication switching. You must install the GitHub CLI and authenticate it with your multiple accounts before setting up automated shell aliases and environment-specific wrappers.

What's the best way to prevent authentication conflicts with personal and work GitHub identities?

The best way to prevent authentication conflicts is to use automated alias setup for your personal and work GitHub identities. This creates context-aware operations with dedicated aliases, ensuring the correct GitHub identity is applied automatically for each repository.

Does this GitHub CLI authentication switching work with PowerShell?

Yes, this GitHub CLI authentication switching works with PowerShell by automatically configuring PowerShell profiles. It creates shell aliases and environment-specific wrappers to handle account switching seamlessly within your Windows workstation environment.

Why does my GitHub CLI push to the wrong account when I have multiple identities configured?

Pushing to the wrong account happens when managing multiple GitHub identities without automated authentication context. By configuring context-aware operations with dedicated aliases, the correct GitHub identity is enforced for specific repositories, eliminating manual overhead.