| name | pipeline-validate-reviews |
| description | Use after pipeline-review-and-plan reviewer reports exist to eliminate false positives and write a prioritized implementation plan from confirmed findings. |
Pipeline Validate Reviews
Validate review findings against source before fixes are planned.
Argument: [review-id]. If omitted, use the most recently modified directory
under .pipeline/review/.
Process
- Locate
.pipeline/review/<review-id>/.
- Read required reports:
security.md, maintainability.md,
clean-code.md, tests.md, developer-experience.md, and bugs.md.
- Read optional reports when present:
frontend.md, contracts.md, and
repo-review-*.md.
- Extract every finding: severity, location, issue, why it matters, fix, and
source reviewer.
- Consolidate duplicates and preference-only findings before validation.
- Validate each finding against actual source and local conventions.
- Classify each finding:
- Confirmed
- False positive
- Verification required
- Blocking investigation
- Write
validation.md.
- Write
implementation-plan.md from confirmed findings only. Include blocking
investigations in a separate section. Keep verification-only checks only in
validation.md.
Validation Standards
Confirm only issues with concrete evidence in the current code. Mark false
positive when the referenced location does not exist, the reviewer misread the
context, the issue is duplicate, or the issue is preference-only.
Use blocking investigation only when a high-risk issue cannot be confirmed
statically but could cause data loss, security exposure, public API breakage, or
broad production outage.
Required Output
validation.md:
# Validation Report
**Review ID**:
**Original findings**:
**After validation**:
## Confirmed Issues
## Blocking Investigations
## Verification Checks
## False Positives Eliminated
implementation-plan.md:
# Implementation Plan
## Confirmed Fixes
## Blocking Investigations Before Merge
If no confirmed fixes are required, still write implementation-plan.md with
No confirmed fixes required.
