skills.rest
sujithatzackriya
sujithatzackriyaCOMMUNITY
Explore all skills by this author →
GitHub

pr-fix

Fix PR review findings one by one with verified commits.

Updated Aug 23, 2026
Search Tags:#typescript#code review#pull request#verification#manual testing#rust#kpi impact
One-click install
npx skills add https://github.com/sujithatzackriya/skills --skill pr-fix-sujithatzackriya
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-fix
Source: https://github.com/sujithatzackriya/skills/tree/main/skills/pr-fix
Command: npx skills add https://github.com/sujithatzackriya/skills --skill pr-fix-sujithatzackriya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a messy PR review feedback thread into a disciplined, one-issue-at-a-time fix process where every change is verified and logged before you ship.

Core Features & Use Cases

  • One-by-one PR finding resolution with per-commit verification: For each review finding, it verifies the issue in the actual code, then runs cargo check (Rust) and pnpm tsc --noEmit (TypeScript) before committing.
  • KPI impact analysis and failure-point logging: It maps each finding to affected KPIs and records the exact failure point and verification outcomes into scripts/ralph/pr-fix-log.md.
  • Manual test gate plus approval before pushing: It requires you to present manual test steps and obtain explicit approval before pushing, preventing “tests passed but behavior didn’t” failures.

Quick Start

Run the pr-fix skill on your existing review doc (for example docs/PR-XXX-Code-Review.md) and let it iterate through each finding, verifying and committing fixes one by one until all approved issues are addressed.

Frequently Asked Questions about pr-fix

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

FAQPage Schema
How do I fix pull request code review findings systematically?▼

To fix pull request code review findings systematically, process an existing review document finding-by-finding. Checkout the branch, resolve issues by ordered severity, and create minimal, verified commits for each fix.

Can I commit code review fixes without manual testing?▼

No, committing code review fixes requires a manual test gate. You must present manual test steps and obtain explicit approval before pushing, ensuring verified behavior rather than just passing automated checks.

Does PR fix verification work with Rust and TypeScript?▼

Yes, PR fix verification works with Rust and TypeScript by enforcing cargo check and pnpm tsc --noEmit before each commit. This ensures code review fixes compile correctly across both languages.

How do I log code review failure points and KPI impacts?▼

You log code review failure points and KPI impacts by mapping each finding to affected KPIs and recording exact verification outcomes into scripts/ralph/pr-fix-log.md during the commit process.

What is the best way to handle PR review feedback one issue at a time?▼

The best way to handle PR review feedback one issue at a time is turning the review thread into a disciplined fix process with per-commit verification, ordered severity handling, and explicit approval before pushing.

Related Skills

Explore More Software Engineering Skills→
lancedblancedb
11.1k

lancedb-update-lance-dependency

Automate Lance dependency updates across Rust and Java components with PR generation.

Official
Advanced
markmhendricksonmarkmhendrickson
27

push

Push the current Git branch to origin with submodule scoping and pre-push checks.

Community
Intermediate
OmarMiraOmarMira

lint-and-validate

Run linting and type checks on Node.js/TypeScript and Python projects.

Community
Intermediate
tvishwanadhatvishwanadha

fix-findings

Cluster verified code-review findings and apply approved fixes interactively.

Community
Advanced