Use when reviewing a pull request with runtime or production evidence — for example to review a PR with runtime verification, gather production evidence, or simulate a patch on live samples. Reviews a pull request by diffing against the PR merge base, checking Runtime History before collecting live samples for remaining gaps, and simulating the patch on captured production inputs.
89%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Provide a single PR review backbone that uses runtime production evidence when possible and falls back to scenario-driven review when runtime verification is incomplete.
Read and follow these references in order. Each phase produces a specific artifact; confirm that artifact exists and meets the phase's exit criteria before advancing to the next phase.
Before moving from one phase to the next, confirm the current phase's exit criteria are met:
pr_base_sha, pr_head_sha, and the PR diff (pr_base_sha → pr_head_sha) are in hand; deployed_sha is recorded when resolved.uncovered or not runtime-verifiable).covered, base-covered, head-covered, or uncovered per Phase 3. Skip live planning and capture when all are covered.base-covered, head-covered, or uncovered verification areas (up to 3).Do not advance a phase until its exit criteria are satisfied; loop back to the prior phase when evidence is incomplete.
pr_base_sha → pr_head_sha) for all verification areas, attribution, findings, runtime assessment, and merge recommendation.deployed_sha only to locate safe runtime instrumentation and describe true deployed production behavior.deployed_sha → pr_head_sha as the PR review diff.base-covered, head-covered, or uncovered. History reads do not require active agents or live-source preflight.At the end of a completed run, emit the full automation response described in Output format. Keep intermediate phase communication in chat using only the content defined for that phase.
lightrun-platform/lightrun-ai
1853b1a
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.