code-review-extras

Detect unreferenced components, residual rule violations, and incorrect ADR claims in code reviews.

Updated Nov 24, 2025
One-click install
npx skills add https://github.com/ByronWilliamsCPA/.claude --skill code-review-extras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-extras
Source: https://github.com/ByronWilliamsCPA/.claude/tree/main/.claude/skills/code-review-extras
Command: npx skills add https://github.com/ByronWilliamsCPA/.claude --skill code-review-extras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill fills critical gaps in standard code reviews by catching high-impact, easy-to-miss defects that prose reads often overlook, reducing post-merge bugs and documentation debt from unreferenced components, leftover rule violations, and incorrect ADR reasoning.

Core Features & Use Cases

  • Reference Graph Pre-Read Pass: Confirms components are imported by deliverable-producing code and documented parameters are actually read at runtime, surfacing "defined but unreferenced" and "documented but unread" defects in seconds via fast grep checks.
  • Full-File Residual Scans: Reviews all repository files (not just PR scope) for leftover rule violations after remediation, classifying residuals as pre-existing or missed in scope to prevent false-alarm triage post-merge.
  • ADR Factual Cross-Checks: Validates ADR technical claims against authoritative code comments to catch incorrect reasoning even when conclusions are correct, preventing future authors from adopting wrong mental models.
  • Use Case: Ideal for use alongside the base code-review skill when reviewing components or model pipelines, SonarCloud/single-rule remediation PRs, or ADRs that document technical constraints.

Quick Start

Use the code-review-extras skill alongside the base code-review skill when reviewing a component's wiring, a remediation PR for residual rule alerts, or an ADR for factual accuracy against code comments.

Frequently Asked Questions about code-review-extras

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

FAQPage Schema
How do I catch unreferenced components during a code review?▼

Perform a full-file residual scan across all repository files rather than just PR scope to find leftover rule violations after remediation, classifying residuals as pre-existing or missed in scope to prevent false-alarm triage post-merge.

How do I validate ADR technical claims against actual code?▼

Validate ADR technical claims by cross-referencing factual statements against authoritative code comments to catch incorrect reasoning, preventing future authors from adopting wrong mental models even when the ADR's conclusions are correct.

Can I review residual SonarCloud rule violations outside the PR scope?▼

Yes, you can review residual SonarCloud rule violations outside the PR scope by running full-file residual scans across the entire repository, classifying leftover alerts as pre-existing or missed in scope to prevent false alarms.

What is the best way to find documented but unread parameters in a model pipeline review?▼

The best way to find documented but unread parameters in a model pipeline review is applying a fast grep-based reference graph check to confirm documented parameters are actually read at runtime.

Does code-review-extras work alongside the base code-review skill for component wiring checks?▼

Yes, code-review-extras works alongside the base code-review skill to augment component wiring checks with high-signal delta checks for unreferenced components, residual rule violations, and incorrect ADR factual claims.