setuplisted

# GitHub Multi-Account Setup ## When to Use This Skill Use when the user: - wants to configure a new or additional GitHub account on this machine - reports git or gh authenticating as the wrong account - asks about SSH host aliases, `includeIf`, `GH_CONFIG_DIR`, or per-repo identity ## What Each Account Needs - an account tree holding its repos - an SSH key - a `Host` alias in `~/.ssh/config` - a git config file - an `includeIf` rule pointing at its account tree - a gh config directory The account tree is the shared input — both tools decide from the path inside it. The next four belong to git, the last to gh. Signing commits adds a second GitHub registration of that same SSH key — see [`references/signing.md`](./references/signing.md). ## Gather Inputs First Before generating any config, establish the user's OS and shell, then ask for their account labels, repo root, usernames, and emails. The references use two accounts named `account1` and `account2`, a repo root of `~/Repos`, and `<username1>` / `<email1>` placeholders. Substitute real values throughout. ## Then Read What the Task Needs | Task | Read | | --- | --- | | Understand the design before changing anything | [`references/layout.md`](./references/layout.md) | | Set up or fix git — SSH keys, host aliases, `includeIf` rules | [`references/git.md`](./references/git.md) | | Set up or fix gh — config directories, `GH_CONFIG_DIR`, the shell hook that selects one | [`references/gh.md`](./references/gh.md) | | Si