Claude-skill-registry diagnose-state

Read state.json and diagnose PR statuses, errors, stuck entries, and anomalies.

install

source · Clone the upstream repo

git clone https://github.com/majiayu000/claude-skill-registry

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/diagnose-state" ~/.claude/skills/majiayu000-claude-skill-registry-diagnose-state && rm -rf "$T"

manifest: skills/data/diagnose-state/SKILL.md

Input

The user may provide an optional argument: a PR identifier like

owner/repo#N

or just

(PR number).

Data Source

Read the state file at

data/state.json

. It follows the

StateFileV2

format defined in

src/types.ts

Top-level:

{ "version": 2, "prs": { "owner/repo#N": PRState, ... } }

Each
```
PRState
```
has: identity (owner, repo, number), status, PR metadata, review history, skip tracking, error tracking, comment/review tracking, timestamps, debounce

If the file doesn't exist or is empty, report that and stop.

Modes

Summary Mode (no argument)

Present a dashboard of all tracked PRs:

Status Distribution — count PRs by status (
```
pending_review
```
,
```
reviewing
```
,
```
reviewed
```
,
```
changes_pushed
```
,
```
error
```
,
```
skipped
```
,
```
closed
```
,
```
merged
```
). Show as a table.

Error Entries — for each PR with

status: "error"

, show:

PR identifier (
```
owner/repo#N
```
)

lastError.phase

lastError.message

lastError.sha

(7 chars),

lastError.occurredAt

```
consecutiveErrors
```
count
Whether it's stuck (consecutiveErrors >=
```
maxRetries
```
from
```
config.yaml
```
, default: 3)

Skipped PRs — for each PR with
```
status: "skipped"
```
, show:
- PR identifier and title
- ```
skipReason
```
  (draft / wip_title / diff_too_large)
- ```
skipDiffLines
```
  if reason is diff_too_large
Anomaly Detection — flag these conditions:
- Any PR in
```
reviewing
```
  status (indicates a crash —
```
store.ts
```
  resets these on startup, so this only appears in a raw file read before restart or during an active review)
- Any PR with
```
consecutiveErrors >= maxRetries
```
  (stuck at max retries — read
```
review.maxRetries
```
  from
```
config.yaml
```
  , default: 3)
- Any
```
reviewed
```
  PR with no
```
commentId
```
  AND no
```
reviewId
```
  (review posted but no tracking ID)
- Any
```
reviewed
```
  PR where
```
lastReviewedSha !== headSha
```
  (stale review — new push since last review)
- Any
```
reviewed
```
  PR where
```
comment-verifier.ts
```
  may have requeued it (reviewId/commentId is null but status is still
```
reviewed
```
  )
Summary Line — total PRs, active (non-terminal), terminal (closed + merged)

Single-PR Mode (with argument)

Look up the PR by key. If only a number is given, search all entries for a matching

number

field. If not found, report that.

Display all fields of the

PRState

grouped:

Identity — owner, repo, number, key
Status — current status, with interpretation
PR Metadata — title, isDraft, headSha (abbreviated to 7 chars), baseBranch
Review History — show
```
lastReviewedSha
```
(7 chars),
```
lastReviewedAt
```
, then format each
```
ReviewRecord
```
as a table row:
- ```
sha
```
  (7 chars) |
```
reviewedAt
```
  |
```
verdict
```
  |
```
posted
```
  | findings count (by severity: issue/suggestion/nitpick/question/praise) |
```
commentId
```
  /
```
reviewId
```
- Show total findings breakdown across all reviews
Skip Tracking — skipReason, skipDiffLines, skippedAtSha
Error Tracking — lastError (phase, message, sha, occurredAt), consecutiveErrors
Comment/Review Tracking — commentId, commentVerifiedAt, reviewId, reviewVerifiedAt
Timestamps — firstSeenAt, updatedAt, closedAt, lastPushAt, lastReviewedAt
Anomalies — same checks as summary mode, applied to this PR

Output Format

Use markdown tables and clear section headers. Keep it scannable. Use ⚠ prefix for anomalies and errors.