github-multi-account

Detect GitHub accounts and configure personal and work aliases.

2|Updated Apr 14, 2026

Search Tags:#automation #devops #authentication #github #gh #aliases #multi-account

Ready to run

npx skills add https://github.com/rett-europe/opentreasury --skill github-multi-account-rett-europe

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-multi-account
Source: https://github.com/rett-europe/opentreasury/tree/main/.copilot/skills/github-multi-account
Command: npx skills add https://github.com/rett-europe/opentreasury --skill github-multi-account-rett-europe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects when multiple GitHub accounts are present and prevents context mix-ups by automatically configuring per-account aliases.

Core Features & Use Cases

Account detection: uses gh auth status to list available accounts.
Alias setup: creates personal/work aliases and wrappers for quick switching.
Workflow safety: ensures commands run against the intended account to avoid cross-context mistakes.

Quick Start

Run gh auth status to detect accounts to designate personal and work accounts so the setup configures aliases 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 and prevent context mix-ups in my terminal?▼

To manage multiple GitHub accounts, this Skill detects existing accounts via gh auth status and generates persistent aliases and wrappers, ensuring repository operations run against the intended work or personal authentication context.

What is the best way to switch GitHub aliases for separate work and personal environments?▼

The best way to switch GitHub aliases is to designate your personal and work accounts during setup; the Skill then creates wrappers that automatically switch authentication contexts to prevent cross-context mistakes in workflows.

Do I need gh auth status configured before setting up multi-account GitHub aliases?▼

Yes, you need gh auth status configured beforehand. The Skill requires gh auth status to identify your available accounts and prompt you to designate them as personal or work before generating the aliases.

How does this automation enforce correct authentication context for GitHub scripts and shells?▼

It enforces correct authentication context by generating persistent wrappers that enforce alias usage, ensuring your scripts and shell commands execute repository operations strictly against the designated GitHub account.

Can I use this to automatically configure GitHub accounts for both scripts and interactive shells?▼

Yes, you can configure GitHub accounts for both scripts and interactive shells. The generated aliases and wrappers ensure correct authentication context is maintained across all workflow, script, and shell repository operations.