providing-code-review

Review pull requests for integration issues and regressions.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill providing-code-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: providing-code-review
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/providing-code-review
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill providing-code-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents superficial or rubber-stamp pull request reviews by enforcing engineering rigor: tracing data flow, checking blast radius, verifying integration boundaries, and validating factual claims before approval.

Core Features & Use Cases

  • Data flow analysis: Trace inputs and outputs for changed functions and new fields to ensure values propagate through all intermediaries.
  • Blast radius verification: Search the entire repository for callers, detect renames/moves/deletes, and ensure all consumers are updated to avoid silent breakage.
  • Integration and CI checks: Confirm API and schema compatibility, verify migrations and config changes, and check that CI and test runs are genuinely passing rather than relying on metadata.
  • Use case: Use when reviewing a teammate's PR that introduces a new field, API change, or file rename to avoid runtime errors and cross-repo integration failures.

Quick Start

Open the pull request, trace where each changed value originates and flows to, search the repo for external callers, confirm integration points and migrations, ensure CI is actually green, and validate any factual claims before approving.

Frequently Asked Questions about providing-code-review

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

FAQPage Schema
How do I trace data flow in a pull request to prevent runtime errors?

Tracing data flow in a pull request involves following changed inputs and outputs through all intermediary functions to ensure new fields propagate correctly. This prevents silent runtime errors caused by incomplete consumer updates.

What is blast radius verification when reviewing code changes?

Blast radius verification is searching the entire repository for callers of modified code to detect renames, moves, or deletes. It ensures all consumers are updated to avoid cross-repo integration failures.

How do I verify CI and test runs are actually passing before merging?

To verify CI and test runs are passing, query CI and deployment APIs directly to validate factual claims rather than relying on metadata. This confirms integration boundaries and schema compatibility before approval.

What is the best way to check API and schema compatibility in a PR review?

The best way to check API and schema compatibility during a PR review is to verify migrations and configuration changes alongside tracing data flow. This ensures integration points remain stable and prevents regressions.

Why does rubber-stamping pull requests cause integration failures?

Rubber-stamping pull requests causes integration failures because it skips tracing data flow, checking blast radius, and verifying integration boundaries. Superficial reviews miss broken callers, leading to silent breakage.

Do I need to query deployment APIs to validate factual claims in a pull request?

Yes, you need to query deployment and CI APIs to validate factual claims in a pull request. Relying on metadata alone is insufficient for confirming that test runs are genuinely passing and integration points are secure.