github-multi-account

Detect multiple GitHub accounts and configure shell aliases for account switching.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/bradygaster/docx-mcp-server --skill github-multi-account
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/bradygaster/docx-mcp-server/tree/main/.squad/templates/skills/github-multi-account
Command: npx skills add https://github.com/bradygaster/docx-mcp-server --skill github-multi-account

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup and management of multiple GitHub accounts, preventing confusion and ensuring the correct account is used for different repositories.

Core Features & Use Cases

  • Account Detection: Automatically identifies if multiple GitHub accounts are configured.
  • User-Friendly Prompting: Asks the user to distinguish between personal and work accounts.
  • Automated Configuration: Sets up shell aliases (ghp, ghw) and command-line wrappers for easy account switching.
  • Use Case: When you frequently switch between personal projects and work-related contributions on GitHub, this skill ensures you always use the right credentials without manual intervention.

Quick Start

Run the github-multi-account skill to set up your personal and work GitHub 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 manage multiple GitHub accounts on the same machine?

To manage multiple GitHub accounts, this skill detects your configured accounts and generates shell aliases for seamless switching. It prompts you to distinguish personal versus work accounts to ensure correct credential usage for repository operations.

How do I switch between personal and work GitHub accounts from the command line?

You can switch accounts using command-line wrappers by configuring shell aliases for personal and work GitHub profiles. The skill sets up specific command aliases, enabling automatic credential switching based on repository ownership.

What is the best way to prevent GitHub from using the wrong account for a repository?

The best way to prevent using the wrong GitHub account is to configure account-locked aliases. This skill automatically applies command-line wrappers that check repository ownership and apply the correct credentials for your git operations.

Do I need to manually configure git credentials to use multiple GitHub accounts?

You do not need to manually configure git credentials for multiple GitHub accounts. The skill automates the entire setup, prompting you to identify personal and work accounts before generating the necessary shell aliases.

How does automated alias generation work for separate GitHub profiles?

Automated alias generation for separate GitHub profiles works by creating distinct shell commands for each account. Once you identify your personal and work accounts, the skill generates wrappers that route repository operations to the correct profile.

Can I use shell aliases to automate GitHub account switching for different repositories?

Yes, you can use shell aliases to automate GitHub account switching. The skill generates specific command-line wrappers that ensure repository operations apply the correct account credentials based on repo ownership.