Guise

guise 🐙🔀

Pick and enforce the right GitHub, Bitbucket or GitLab account per repository.

For teams where every developer has more than one account on the same machine (personal + company, multiple orgs, client accounts…). guise remembers which account this repo should use, activates it before any gh / push / PR operation, and warns when your git email is wrong — all without ever storing a token.

• GitHub — switches the active account via gh auth switch.
• Bitbucket & GitLab — no account CLI exists, so guise pins the right SSH key per repo (via local core.sshCommand) + git identity. That key is the account that pushes.

It ships as both a standalone CLI and a Claude Code plugin (skills, hooks, and a status line that shows the active account).

[github account: john-work · [email protected]]

---

The problem it solves

You clone acme/web-app. Your machine has two GitHub accounts logged in to gh: john-personal (default) and john-work. You open Claude Code, ask it to create a PR — and it uses the wrong account, or your commit lands with your personal @gmail.com email. guise fixes the account per repo, so the right identity is always used and verified before GitHub work.

---

Install

Quick (community installer)

macOS / Linux / WSL:

curl -fsSL https://raw.githubusercontent.com/brunomilani/guise/main/install.sh | bash

Windows PowerShell:

irm https://raw.githubusercontent.com/brunomilani/guise/main/install.ps1 | iex

From source

git clone https://github.com/brunomilani/guise
cd guise
npm install
npm run build
npm test
npm link        # makes `guise` available globally

As a Claude Code plugin

/plugin marketplace add brunomilani/guise
/plugin install guise@guise

This adds the /guise command (plus the /guise:* skills), the SessionStart / pre-Bash hooks, and makes the bundled CLI available to those hooks. (Installing the plugin and npm link are independent — do either or both.)

---

Usage (individual)

cd /path/to/repo
guise init        # detect repo, list gh accounts, pick one (saved locally)
guise status      # full report
guise use         # activate the chosen account via `gh auth switch`
guise validate    # exit non-zero if anything is wrong
guise git-sync    # apply user.name / user.email locally (asks first)
guise install-hook # enforce the account on every push, from any terminal
guise reset       # forget the choice for this repo

Commands

Command	What it does
init	Auto-detects the right account (matches repo owner → account, or picks the only one) and saves it. Prompts only when genuinely ambiguous. Flags: --user, --email, --ssh-key, --auto, --yes, --force.
set	Non-interactive: guise set --user X [--email E] [--ssh-key path]. Ideal for scripts/CI and for Claude to run inside a session.
status	Repo + remote + configured account + active gh account + git identity + policy + validation.
choose	Change the chosen account for this repo.
use	Activate the configured account. GitHub: gh auth switch. Bitbucket/GitLab: pin the repo-local SSH key.
validate	Runs every check. Non-zero exit on error (CI-friendly).
git-sync	Sets git config --local user.name/email from the saved choice (after confirmation).
install-hook	Installs a native git pre-push hook that runs use + validate before every push — so the account is enforced in any terminal, not only inside a Claude session. Never clobbers an existing non-guise hook.
uninstall-hook	Removes the guise pre-push hook (only when guise owns it).
reset	Removes the local mapping for this repo.
statusline	Prints [github account: …] for the Claude Code status line.

Inside Claude Code, use the /guise command with any subcommand as an argument — e.g. /guise status, /guise use, /guise validate, /guise choose (no argument defaults to status). The individual skills are also available namespaced: /guise:init, /guise:status, /guise:use, /guise:validate, /guise:choose, /guise:git-sync, /guise:install-hook, /guise:reset.

---

Providers: GitHub + Bitbucket + GitLab

guise actively manages three providers, each with the mechanism that fits it:

Provider	How "use" activates the account	Account discovery
GitHub	gh auth switch to the chosen account	Automatic via gh auth status
Bitbucket	Pins the repo-local SSH key (core.sshCommand) + git identity	Manual / auto-detected from ~/.ssh/config
GitLab	Same SSH model as Bitbucket	Manual / auto-detected from ~/.ssh/config