github-multi-account

Detect multiple GitHub accounts and configure persistent gh personal/work aliases.

Updated Nov 11, 2025
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill github-multi-account-acmeleme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/github-multi-account
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill github-multi-account-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and configure GitHub personal/work aliases for multi-account setups.

Core Features & Use Cases

  • Detect multiple GitHub accounts via gh auth status and list them.
  • Create safe, persistent aliases (ghp for personal, ghw for work).
  • Update user profile and PATH so aliases load in every session.

Quick Start

Install the skill and, when you have multiple GitHub accounts, follow the prompts to bind 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 configure GitHub aliases for multiple accounts in PowerShell?

To configure GitHub aliases for multiple accounts, the Skill detects accounts via gh auth status, prompts you to designate personal and work profiles, and creates persistent gh-personal and gh-work functions in your PowerShell environment.

How does multi-account GitHub detection work before creating aliases?

Multi-account GitHub detection works by checking gh auth status for two or more authenticated accounts. Once detected, it prompts you to bind specific profiles to personal and work aliases for safe separation.

Do I need to update my PowerShell profile manually to keep GitHub aliases persistent?

You do not need to update your PowerShell profile manually. The Skill automatically updates your profile, persists aliases to a bin directory, and modifies PATH to ensure gh-personal and gh-work load in every new session.

What is the best way to separate personal and work GitHub accounts on Windows?

The best way to separate personal and work GitHub accounts is by using this Skill to generate distinct gh-personal and gh-work aliases, which automatically persist across terminal sessions via PowerShell profile integration.

Why are my GitHub multi-account aliases not working in new PowerShell sessions?

GitHub multi-account aliases fail in new sessions if PATH or profile updates are missing. This Skill resolves that by persisting alias functions to a bin directory and applying PowerShell profile updates to ensure continuous availability.

Can I use this Skill if gh auth status only shows one GitHub account?

You cannot use this Skill with only one GitHub account. It specifically applies when gh auth status shows two or more accounts, prompting you to designate which profile is personal and which is work before generating aliases.