diagnose-state

Diagnose PR state from data/state.json and validate StateFileV2 schema.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill diagnose-state
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnose-state
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/diagnose-state
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill diagnose-state

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and summarize PR state by reading data/state.json to surface statuses, errors, and anomalies.

Core Features & Use Cases

  • Reads StateFileV2 to provide dashboards and single-PR views.
  • Detects patterns like stalled reviews, repeated errors, and stale reviews, aiding triage.
  • Enables quick decisions for maintainers to fix PR review flows.

Quick Start

Run the diagnose-state skill on the repo's state file to get a current PR-state snapshot and anomaly flags.

Frequently Asked Questions about diagnose-state

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

FAQPage Schema
How do I diagnose PR state and surface anomalies from state.json?

To diagnose PR state, the tool reads data/state.json to validate the StateFileV2 schema and summarize statuses, errors, and anomalies. It detects patterns like stalled or stale reviews to aid triage.

What is the best way to triage stalled PR reviews across multiple tracked pull requests?

The best way to triage stalled PR reviews is using the summary dashboard, which reads state.json to surface statuses and anomalies across all tracked PRs. It highlights repeated errors and stale reviews for quick maintainer decisions.

How does anomaly detection work for PR review states based on configurable thresholds?

Anomaly detection for PR review states works by reading configurable thresholds from config.yaml and validating them against the StateFileV2 data. It flags stalled reviews and repeated errors based on these defined limits.

Can I inspect detailed fields and histories for a single PR in the state.json file?

Yes, you can inspect detailed fields and histories for a single PR using the single-PR view. This mode reads the StateFileV2 data to provide a focused diagnostic summary of individual pull request states and errors.

Do I need a specific schema format in state.json to run PR diagnostics?

Yes, you need the StateFileV2 schema format in data/state.json to run PR diagnostics. The tool validates the state file against this schema before reporting actionable insights and anomalies.

Why are my PR state anomalies not showing up in the diagnostic dashboard?

PR state anomalies may not show up if the configurable thresholds in config.yaml are not properly set or if the state.json file fails the StateFileV2 schema validation. The tool requires valid data to flag anomalies.