How do I install the Github Windows Auth skill?

Run npx skillmds@latest add aibot88/github-windows-auth in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Github Windows Auth safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Github Windows Auth?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Github Windows Auth free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Github Windows Auth?

aibot88 (@aibot88) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Github Windows Auth by aibot88 — Agent Skill

Name: Github Windows Auth
Rating: 4.5 (4 reviews)
Author: aibot88

Github Windows Auth

Diagnose and fix GitHub authentication issues on Windows when pushing fails with "Repository not found" or wrong-account errors. Use when git push fails despite the repo existing, when multiple GitHub accounts are in play (personal + org), or when Windows Credential Manager has stale credentials. Trigger on phrases like "push failed", "repository not found", "wrong account", "gh auth", "credential", "git push 403", or any push error after a gh auth login.

aibot88 Updated Sep 9, 2026 3 repo stars

File contents

GitHub Windows Auth — Diagnose & Fix

Fix git push failures on Windows caused by stale credentials or mismatched GitHub accounts.

The pattern

On Windows, git uses the Windows Credential Manager as its credential store. When multiple GitHub accounts are in use (e.g. personal bmaltais and org bernardmaltais), the stored credential can belong to the wrong account — and gh auth switch alone doesn't fix it because git bypasses gh and reads the cached token directly.

The fix is always the same three steps:

Clear the stale Windows credential
Tell git to use gh as its credential helper going forward
Push

Diagnostic process

Step 1 — Identify which account the remote needs

git -C <repo-path> remote get-url origin

The org/user in the URL tells you which gh account must be active.

Step 2 — Check which accounts `gh` knows about

gh auth status

Look for the account matching the remote. If it's not listed, authenticate it first:

gh auth login

Step 3 — Switch `gh` active account if needed

gh auth switch --user <username>

Step 4 — Clear stale Windows credential and wire `gh` as helper

cmdkey /delete:LegacyGeneric:target=git:https://github.com
gh auth setup-git

Step 5 — Push

git -C <repo-path> push

Notes

gh auth setup-git writes gh auth git-credential as the credential helper in the global git config. It persists — you only need to run it once per machine (or after cmdkey /delete wipes the old entry).
If you have two org accounts (e.g. bmaltais and bernardmaltais), the active gh account at push time determines which token git uses. Switch before pushing to the other org.

If gh is not on PATH in the current shell, reload it first:

$env:PATH = [System.Environment]::GetEnvironmentVariable("PATH","User") + ";" + [System.Environment]::GetEnvironmentVariable("PATH","Machine")

Quick reference — full fix in one line

$env:PATH = [System.Environment]::GetEnvironmentVariable("PATH","User") + ";" + [System.Environment]::GetEnvironmentVariable("PATH","Machine")
gh auth switch --user <username>
cmdkey /delete:LegacyGeneric:target=git:https://github.com
gh auth setup-git
git -C <repo-path> push

---name: github-windows-authdescription: Diagnose and fix GitHub authentication issues on Windows when pushing fails with "Repository not found" or wrong-account errors. Use when git push fails despite the repo existing, when multiple GitHub accounts are in play (personal + org), or when Windows Credential Manager has stale credentials. Trigger on phrases like "push failed", "repository not found", "wrong account", "gh auth", "credential", "git push 403", or any push error after a gh auth login.--- # GitHub Windows Auth — Diagnose & Fix Fix `git push` failures on Windows caused by stale credentials or mismatched GitHub accounts. ## The pattern On Windows, git uses the **Windows Credential Manager** as its credential store. When multiple GitHub accounts are in use (e.g. personal `bmaltais` and org `bernardmaltais`), the stored credential can belong to the wrong account — and `gh auth switch` alone doesn't fix it because git bypasses `gh` and reads the cached token directly. The fix is always the same three steps: 1. Clear the stale Windows credential 2. Tell git to use `gh` as its credential helper going forward 3. Push ## Diagnostic process ### Step 1 — Identify which account the remote needs ```powershell git -C <repo-path> remote get-url origin ``` The org/user in the URL tells you which `gh` account must be active. ### Step 2 — Check which accounts `gh` knows about ```powershell gh auth status ``` Look for the account matching the remote. If it's not listed, authenticate it first: ```powershell gh auth login ``` ### Step 3 — Switch `gh` active account if needed ```powershell gh auth switch --user <username> ``` ### Step 4 — Clear stale Windows credential and wire `gh` as helper ```powershell cmdkey /delete:LegacyGeneric:target=git:https://github.com gh auth setup-git ``` ### Step 5 — Push ```powershell git -C <repo-path> push ``` ## Notes - `gh auth setup-git` writes `gh auth git-credential` as the credential helper in the global git config. It persists — you only need to run it once per machine (or after `cmdkey /delete` wipes the old entry). - If you have **two org accounts** (e.g. `bmaltais` and `bernardmaltais`), the active `gh` account at push time determines which token git uses. Switch before pushing to the other org. - If `gh` is not on `PATH` in the current shell, reload it first: ```powershell $env:PATH = [System.Environment]::GetEnvironmentVariable("PATH","User") + ";" + [System.Environment]::GetEnvironmentVariable("PATH","Machine") ``` ## Quick reference — full fix in one line ```powershell $env:PATH = [System.Environment]::GetEnvironmentVariable("PATH","User") + ";" + [System.Environment]::GetEnvironmentVariable("PATH","Machine") gh auth switch --user <username> cmdkey /delete:LegacyGeneric:target=git:https://github.com gh auth setup-git git -C <repo-path> push ```

Frequently asked questions