skills.rest
martin-janci
martin-janciCOMMUNITY
Explore all skills by this author →
GitHub

debug-review

Trace a PR through the claude-code-reviewer pipeline to diagnose review failures.

Updated Jan 30, 2026
Search Tags:#debugging#pipeline#tracing#diagnosis#pr-review#claude-code-reviewer
One-click install
npx skills add https://github.com/martin-janci/claude-code-reviewer --skill debug-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-review
Source: https://github.com/martin-janci/claude-code-reviewer/tree/main/.claude/skills/debug-review
Command: npx skills add https://github.com/martin-janci/claude-code-reviewer --skill debug-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses PR review failures by tracing a PR through Claude Code Reviewer's pipeline to surface actionable diagnoses.

Core Features & Use Cases

  • End-to-end PR review tracing: loads PR state, analyzes errors, reviews history, and generates a diagnosis.
  • Interactive guidance: step-by-step insights to identify root causes and blockers.
  • Reproducible checks: verifies diff size, clone/worktree status, and review gating logic for debugging.

Quick Start

Provide a PR identifier (owner/repo#N or N) to start the diagnostic flow.

Frequently Asked Questions about debug-review

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

FAQPage Schema
How do I diagnose a PR review failure in my pipeline?▼

Diagnosing a PR review failure involves tracing the PR through the claude-code-reviewer pipeline to surface root causes. Provide a PR identifier like owner/repo#N or N to load state and analyze errors.

Why does my PR review fail the gating checks?▼

PR review gating failures stem from diff size limits or clone/worktree status issues. Reproducible checks verify these conditions to pinpoint the exact blocker preventing the pipeline from proceeding.

What is the best way to trace a PR through a code reviewer pipeline?▼

Tracing a PR through a code reviewer pipeline involves loading PR state, analyzing errors, reviewing history, and generating a diagnosis with step-by-step insights to identify root causes and blockers.

Can I debug post-merge QA pipeline checks for a specific PR?▼

Yes, you can debug post-merge QA pipeline checks by supplying the PR identifier. The diagnostic flow loads the PR state, analyzes errors, and guides remediation to surface root causes for production reviews.

How do I identify the root cause of a blocked code review?▼

Identifying the root cause of a blocked code review requires applying diagnostic steps to the loaded PR state. This surfaces actionable insights and recommended remediation steps for the specific failure.

Related Skills

Explore More Software Engineering Skills→
lugassawanlugassawan
2

workflow-pr-review-followup

Re-run reviewer agent on updated PR diffs and deduplicate feedback against existing GitHub review threads.

Community
Advanced
willietranwillietran
3

qa-fixer

Automate QA gate failure remediation with worktree creation and retry logic.

Community
Advanced
xiaoquqixiaoquqi

code-insights-redesign

Automate code-review workflows with full-clone history and structured summaries.

Community
Advanced
gtheysgtheys
4

debug

Investigate minikube pod logs, PostgreSQL nonprod state, and git history.

Community
Intermediate