github-multi-account

Configure PowerShell profiles and PATH variables for GitHub CLI account aliases.

41|8|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/tamirdresher/squad-skills --skill github-multi-account-tamirdresher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/tamirdresher/squad-skills/tree/main/plugins/github-multi-account
Command: npx skills add https://github.com/tamirdresher/squad-skills --skill github-multi-account-tamirdresher

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill eliminates the chaos and potential for error associated with managing multiple GitHub accounts, ensuring commands are always executed in the correct context.

Core Features & Use Cases

  • Account-Locked Aliases: Creates distinct aliases (ghp, ghw) that automatically switch to the correct GitHub account before executing any command.
  • Automated Setup: The AI handles the detection of accounts, user confirmation, and the necessary configuration in PowerShell profiles and PATH environment variables.
  • Use Case: When working on both personal projects and company repositories, you can use ghp for personal tasks and ghw for work tasks, preventing accidental commits or pushes to the wrong account.

Quick Start

Tell your AI to set up your GitHub multi-account aliases.

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 from the command line?

You can switch between multiple GitHub accounts from the command line by setting up account-locked aliases. This creates specific command shortcuts like `ghp` and `ghw` that automatically execute commands under your personal or work GitHub identity.

Can I prevent accidental commits to the wrong GitHub account?

You can prevent accidental commits to the wrong GitHub account by using distinct command aliases for different accounts. This ensures commands are always executed in the correct context, eliminating the chaos and potential for error.

What do I need to set up GitHub CLI aliases for personal and work accounts?

To set up GitHub CLI aliases for personal and work accounts, you need the GitHub CLI and a PowerShell or CMD runtime environment. The setup process detects your accounts, prompts for designations, and configures your PowerShell profile.

How does automated multi-account GitHub CLI setup work?

Automated multi-account GitHub CLI setup works by detecting user accounts and prompting for personal and work designations. It then configures PowerShell profiles and PATH environment variables to create seamless switching aliases.

Are there limitations to using account-locked aliases for GitHub CLI?

The primary limitation of using account-locked aliases for GitHub CLI is the runtime requirement; you must have PowerShell or CMD environments and the GitHub CLI installed. The setup is also focused on CLI interactions rather than GUI-based git clients.