github-multi-account

Detect GitHub accounts and configure aliases for switching personal and work contexts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects multiple GitHub accounts and configures persistent aliases to switch between personal and work contexts without manual gh auth switching.

Core Features & Use Cases

  • Detect multiple GitHub accounts, prompt user to identify personal vs work, and automatically set up aliases and wrappers.
  • Create shell and environment changes to switch gh contexts quickly across sessions.
  • Use case: a developer with personal and organization repos can operate without manually switching accounts.

Quick Start

Run the skill to detect your GitHub accounts, answer the prompt, and let it set up 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 switch between personal and work GitHub accounts without manual auth?

Switch GitHub accounts without manual auth by detecting multiple logged-in gh profiles and configuring persistent shell aliases. This automatically updates your environment variables and wrapper commands to instantly switch personal and work contexts across sessions.

Can I use shell aliases to manage multiple GitHub accounts in PowerShell and CMD?

You can manage multiple GitHub accounts in PowerShell and CMD by applying profile updates and wrapper commands. The system detects your accounts and sets up session-specific aliases to reliably switch contexts across both shell environments.

What is the best way to automate GitHub multi-account context switching for development?

Automate GitHub multi-account context switching by detecting existing accounts and prompting user identification. It automatically configures shell profile updates and wrapper commands to maintain separate personal and work environments without manual intervention.

How do I configure persistent GitHub aliases to separate personal and organization repos?

Configure persistent GitHub aliases by running a detection process that identifies your accounts and prompts for personal versus work designation. It automatically applies shell and PATH updates to create reliable wrapper commands for organization repos.

Does GitHub multi-account alias switching work across different terminal sessions?

GitHub multi-account alias switching works across different terminal sessions by applying persistent shell and profile updates. Once configured, the wrappers ensure your selected personal or work context remains active in new PowerShell and CMD sessions.

Why does my GitHub account context not persist when opening a new shell?

Your GitHub account context fails to persist if shell profiles lack proper alias configuration. By applying persistent PATH updates and wrapper commands, the context automatically switches and remains reliably active across new sessions.