review-feedback-promoter

Convert recurring code review findings into automated harness checks or documentation.

3|Updated Jun 8, 2026

Search Tags:#quality assurance #code review #defect prevention #repeated findings #harness promotion

Ready to run

npx skills add https://github.com/pax-k/pax-fullstack-harness --skill review-feedback-promoter

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-feedback-promoter
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/review-feedback-promoter
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill review-feedback-promoter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the issue of repetitive review findings during code reviews, helping to convert them into reusable harness checks or documentation to prevent future occurrences.

Core Features & Use Cases

Review Feedback Analysis: Identify recurring review findings across various review outputs.
Check Promotion: Convert findings into checks, such as documentation rules, tests, lint rules, or boundary checks.
Specialized Fix Routing: Direct specialized fixes to relevant tools for governance and consistency gaps.
Validation and Completion: Ensure that each promotion corresponds to a real finding and is specific enough to avoid false positives.

Quick Start

Use the review-feedback-promoter skill to create a new harness check based on a repeated code review finding.

Frequently Asked Questions about review-feedback-promoter

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

FAQPage Schema

How do I convert recurring code review findings into automated checks?▼

You can convert recurring code review findings into automated checks by promoting them into durable harness defenses like lint rules, boundary checks, or tests to prevent repeated defects and ensure consistency across reviews.

What is the best way to stop repetitive review feedback from recurring in pull requests?▼

Stopping repetitive review feedback involves analyzing repeated findings and promoting them into documentation rules or automated harness checks, ensuring that previously identified governance and consistency gaps are validated and automatically prevented.

Can I route specialized code review fixes to specific governance tools?▼

Yes, specialized review fixes can be routed to relevant tools for governance and consistency gaps, directly directing specific remediations while validating that each promoted check corresponds to a real finding to avoid false positives.

How do I validate that a promoted harness check avoids false positives?▼

Validating a promoted harness check requires ensuring each promotion corresponds to a real, recurring review finding and is specific enough to avoid false positives, confirming the automated check accurately targets the intended defect prevention scenario.

Does review feedback promotion work for engineering teams without existing test harnesses?▼

Review feedback promotion suits engineering teams facing repetitive findings needing conversion into automated defenses, but implementing durable harness checks or documentation rules requires a baseline environment to execute the promoted scripts and validate governance.