repo-path-sanity

Diagnose Git credential and remote configuration failures and produce executable fix commands.

6|1|Updated May 11, 2026
One-click install
npx skills add https://github.com/yakeworld/Synthos --skill repo-path-sanity-yakeworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-path-sanity
Source: https://github.com/yakeworld/Synthos/tree/main/skills/private/extended/external-automation/repo-path-sanity
Command: npx skills add https://github.com/yakeworld/Synthos --skill repo-path-sanity-yakeworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Git operations like pushing over HTTPS or creating pull requests with gh fail for opaque reasons: global gitconfig entries hijack remotes, credential helpers conflict, and PATs lack write scopes. This Skill traces the actual configuration source and returns a problem-to-root-cause-to-fix report instead of guesswork. ## Core Features & Use Cases - Configuration Tracing: Runs git config --list --show-origin to locate insteadOf rewrites and credential.helper overrides in global versus repo-level config. - Auth Diagnosis: Distinguishes being logged in via gh auth status from actually having repo and write:repository PAT scopes, and checks SSH key registration. - NFS-Safe Operation: Uses timeout-bounded shallow commands on slow NFS mounts where full traversal would hang at 300 seconds. - Use Case: When gh pr create fails with "not accessible" despite a successful login, the Skill identifies the missing PAT scope and outputs the exact remediation steps. ## Quick Start Diagnose why gh pr create fails in my repository at /work/proj and give me the exact fix commands.

Frequently Asked Questions about repo-path-sanity

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix gh pr create failing with not accessible?

Run gh auth status to confirm login, then check your PAT scopes. Being logged in does not imply write access; the token needs repo and write:repository scopes. Create a new Classic PAT with those scopes in GitHub Developer settings.

Why does my HTTPS Git remote get converted to SSH?

A url.https://github.com/.insteadOf entry in your global ~/.gitconfig rewrites HTTPS remotes to SSH. Find it with git config --list --show-origin, then remove it using git config --global --unset url.https://github.com/.insteadOf.

How do I trace where a Git config value comes from?

Use git config --list --show-origin to display every setting with the file that defined it. This reveals whether a credential.helper or insteadOf rule comes from the global ~/.gitconfig or the repo-level config, which matters because global settings can override gh auth git-credential.

Why does ssh -vT [email protected] return Permission denied publickey?

The SSH key on your machine is not registered to your GitHub account. Add the public key under GitHub Settings, SSH keys, then retry the connection test to confirm authentication succeeds.

Can I run Git diagnostics on an NFS-mounted repository?

Yes, but avoid full directory traversal. NFS mounts are extremely slow, so os.walk or du -sh can hit 300-second timeouts. Wrap every diagnostic in timeout and use shallow commands like a single git config query instead of scanning the tree.