git:20261010.eb14d4f to git:20261010.d5feb4c

10 added, 10 removed. Audit A to A.

---

name: doctor

description: Check an existing PS1 decomp repository against psxdecomp's tested pins — PA3 version, the kit's install record, the interpreter, the ROM firewall, the reference library. Read-only. Invoked as /psxdecomp:doctor.

disable-model-invocation: true

argument-hint: "[--repo DIR]"

---

# /psxdecomp:doctor

Read-only. Run `"${CLAUDE_PLUGIN_ROOT}/scripts/psxd" preflight --target . --resume --dry-run` only if the developer asks

about the machine; otherwise just:

```

"${CLAUDE_PLUGIN_ROOT}/scripts/psxd" doctor --repo ${ARGUMENTS:-.}

```

Report the `FAIL` and `WARN` rows, one line each, with the fix each row names. Two rows are WARN only and use the

network: `progress` (when a workflow builds a decomp.dev report: its safety lint, and whether decomp.dev lists the

- repository) and `github` (the repository's security settings through `gh api`; each WARN carries the `gh api` command

- that fixes it, for the developer to run). `--offline` skips both; `--only github` runs just that row. In split mode

- `github` checks only that origin, the `-dev`, is private (a FAIL otherwise: dev's history is exposed), and two more

- use `gh api`: `private-repo` FAILs when `<game>-private` breaks its rules (public, forked, Actions on, a

- writable or second deploy key, another collaborator, a `private_rev` it lacks), and `public-standard` WARNs with the

- public repository's drift from the standard (`settings --apply` fixes it, the developer's). For drift in the reference

- library the fix is `"${CLAUDE_PLUGIN_ROOT}/scripts/psxd" fetch_refs --repo .`; for a repository not bootstrapped by

- psxdecomp it is `/psxdecomp:upgrade`. A README lint failure names its fix (the standard: `docs/PUBLISHING.md` in the

- plugin); the generated blocks are `python3 tools/psxd_publish.py render README.md --write`. Never fix anything from

- this skill: it diagnoses.

+ repository, in split mode the public `[public].repo`) and `github` (the repository's security settings through `gh api`;

+ each WARN carries the `gh api` command that fixes it, for the developer to run). `--offline` skips both; `--only github`

+ runs just that row. In split mode `github` checks only that origin, the `-dev`, is private (a FAIL otherwise: dev's

+ history is exposed), and two more use `gh api`: `private-repo` FAILs when `<game>-private` breaks its rules (public,

+ forked, Actions on, a writable or second deploy key, another collaborator, a `private_rev` it lacks), and

+ `public-standard` WARNs with the public repository's drift from the standard (`settings --apply` fixes it, the

+ developer's). For drift in the reference library the fix is `"${CLAUDE_PLUGIN_ROOT}/scripts/psxd" fetch_refs --repo .`;

+ for a repository not bootstrapped by psxdecomp it is `/psxdecomp:upgrade`. A README lint failure names its fix (the

+ standard: `docs/PUBLISHING.md` in the plugin); the generated blocks are

+ `python3 tools/psxd_publish.py render README.md --write`. Never fix anything from this skill: it diagnoses.