github-multi-account

Detect GitHub accounts and configure personal and work aliases via PowerShell and CMD wrappers.

7|Updated Oct 24, 2020
One-click install
npx skills add https://github.com/snow-jallen/HomeSpeaker --skill github-multi-account-snow-jallen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/snow-jallen/HomeSpeaker/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/snow-jallen/HomeSpeaker --skill github-multi-account-snow-jallen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and set up account-locked gh aliases for multi-account GitHub. The AI reads this skill, detects accounts, asks the user which is personal/work, and runs the setup automatically.

Core Features & Use Cases

  • Detect accounts by running gh auth status and listing the authenticated users.
  • Prompt the user to label each account as personal or work and confirm the intended binding.
  • Set up gh aliases by creating PowerShell functions (gh-personal, gh-work) and CMD wrappers, and update PATH automatically.
  • Persist the configuration in the user's environment and verify in-session that aliases resolve to the correct accounts.

Quick Start

Run gh auth status to detect accounts, then configure personal and work 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 manage multiple GitHub accounts with gh CLI?

You can manage multiple GitHub accounts by using this Skill to detect authenticated users via gh auth status, label them as personal or work, and automatically generate PowerShell functions and CMD wrappers for account-locked aliases.

Can I create PowerShell aliases for different GitHub accounts?

Yes, you can create PowerShell aliases for different GitHub accounts. The Skill sets up distinct PowerShell functions like gh-personal and gh-work, updates the PATH, and verifies the aliases resolve to the correct accounts within your 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 on Windows is to use this Skill to detect your authenticated users, label them, and apply automated setup for PowerShell functions and CMD wrappers that lock commands to specific accounts.

Does setting up gh multi-account aliases require manual PATH configuration?

Setting up gh multi-account aliases does not require manual PATH configuration. The Skill automatically updates your PATH when creating the PowerShell functions and CMD wrappers for your personal and work accounts.

Why do my gh aliases not resolve to the correct GitHub account after setup?

If gh aliases do not resolve to the correct account, it may be due to an incomplete setup. This Skill includes in-session verification to confirm that your personal and work aliases bind to the intended accounts after configuration.