GitHub PAT Debugging

排查 GitHub PAT 认证失败、401、Bad credentials、推送失败、token 看起来失效等问题。先检查命令、变量传递、路径和请求参数，再用 curl、Node、Python 或 PowerShell 交叉验证，确认后才判断权限、撤销或网络原因。适用于 GitHub API、Contents API、GitHub Pages 和 Skill 镜像推送。 Diagnose GitHub Personal Access Token failures before declaring a token expired or revoked.

as observed 2026-09-08T10:18:19.295Z

Identifier: github-pat-debugging
Source: ClawHub
Version observed: 1.0.3
Source repository: not published
Repository observation: No source repository listed
First observed here: 2026-08-28T22:06:34.671Z
Observations recorded: 2
Installs (reported upstream): 0
Weekly downloads (upstream): 223

Observation history

2026-09-08T10:18:19.295Z

Fields that differed: changelog description latestVersion summary

Field	Before	After
`changelog`	"Add not_for field (agent routing exclusion) per skill-design-guide Principle Two: agent-consumption-first design"	"Add private-repo 404 rule: unauthenticated 404 on pages/raw is privacy hiding, not deletion; confirm via authenticated GET /repos 200 + private:true"
`description`	"Diagnose GitHub Personal Access Token failures — 401 Bad credentials, push failures, tokens that appear valid but fail — before declaring them expired or revoked. Checks the comma	"排查 GitHub PAT 认证失败、401、Bad credentials、推送失败、token 看起来失效等问题。先检查命令、变量传递、路径和请求参数，再用 curl、Node、Python 或 PowerShell 交叉验证，确认后才判断权限、撤销或网络原因。适用于 GitHub API、Contents API、GitHub Pages 和 Ski
`latestVersion`	"1.0.2"	"1.0.3"
`summary`	"Diagnose GitHub Personal Access Token failures — 401 Bad credentials, push failures, tokens that appear valid but fail — before declaring them expired or revoked. Checks the comma	"排查 GitHub PAT 认证失败、401、Bad credentials、推送失败、token 看起来失效等问题。先检查命令、变量传递、路径和请求参数，再用 curl、Node、Python 或 PowerShell 交叉验证，确认后才判断权限、撤销或网络原因。适用于 GitHub API、Contents API、GitHub Pages 和 Ski

Correction

If you maintain this extension and believe anything above is inaccurate, request a correction. Corrections are published, and disputed entries are marked as disputed while under review.