Pr Feedback Quality Gate
- 896 installs
- 83.7k repo stars
- Updated August 5, 2026
- nexu-io/open-design
pr-feedback-quality-gate is a pull request workflow skill that tracks review feedback, resolves merge conflicts, validates fixes, and runs a read-only cross-review before committing follow-up changes for developers manag
About
pr-feedback-quality-gate is an Open Design utility skill for safe pull request follow-up. It starts by inspecting PR state—comments, reviews, mergeability, checks, branch, and local worktree status—while keeping unrelated local changes out of the PR. The workflow addresses review comments and merge conflicts, validates fixes, and applies a read-only cross-review before commit or push. Triggers include PR feedback, review comments, merge conflicts, cross-review, Claude CLI review, and monitor PR. Developers reach for pr-feedback-quality-gate when a PR needs structured remediation instead of ad hoc edits that miss checks or introduce scope creep.
- 6-step PR feedback quality gate workflow
- Isolated worktree for dirty checkouts or concurrent agent use
- Smallest-safe-fix rule that preserves upstream structure
- Narrow validation then full repository gates including pnpm guard
- Read-only cross-review before commit or push with strict evidence rules
Pr Feedback Quality Gate by the numbers
- 896 all-time installs (skills.sh)
- +74 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #156 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/nexu-io/open-design --skill pr-feedback-quality-gateAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 896 |
|---|---|
| repo stars | ★ 83.7k |
| Last updated | August 5, 2026 |
| Repository | nexu-io/open-design ↗ |
How do you safely address pull request review feedback?
Safely handle PR feedback, resolve merge conflicts, validate fixes, and run a read-only cross-review before committing changes.
Who is it for?
Developers with open PRs carrying review comments, failing checks, or merge conflicts who want a gated follow-up workflow.
Skip if: Developers starting a greenfield feature branch with no open PR or review feedback should skip pr-feedback-quality-gate.
When should I use this skill?
A developer mentions PR feedback, review comments, merge conflicts, cross-review, or monitoring an open pull request for fixes.
What you get
Resolved review threads, merged conflict fixes, validated changes, and cross-review notes before push.
- Resolved PR feedback
- Cross-review validation notes
Files
PR Feedback Quality Gate
Use this when a PR has review feedback, merge conflicts, pending checks, or needs a monitored follow-up after a fix.
Workflow
1. Inspect PR state first: comments, reviews, mergeability, checks, branch, and local worktree status. Keep unrelated local changes out of the PR. 2. Use an isolated worktree for review fixes or conflict resolution when the main checkout is dirty, behind remote, or being used by another agent. 3. Make the smallest safe fix. Preserve the original bug invariant and any newer upstream structure introduced by main. 4. Run the narrow validation first, then the repository-required gates. For this repo, include pnpm guard; add package typechecks/builds/tests when touched files require them. 5. Before commit or push, run a read-only cross-review of the staged or proposed diff. Forbid file edits and git write or coordination commands. 6. Treat cross-review as evidence, not authority. Accept only findings grounded in the diff, repository rules, user goal, or validation results. Downgrade or reject style preferences, broad scope expansion, and suggestions that conflict with safety or ownership boundaries; record the reason briefly. 7. If accepted blockers remain, fix them, rerun validation, and repeat the review. Commit and push only after validation passes and there are no accepted blockers.
Monitoring cadence
- Active review or failing checks: check often enough to unblock quickly.
- Clean or approved PR waiting for merge: check about every 12 hours.
- Merged PR: reduce to daily lightweight observation for CI, release, or
regression signals, and stop making code changes unless asked.
Report
Always report PR state, actions taken, cross-review verdict, accepted or rejected findings, validation run, commits pushed, skipped checks with reasons, remaining risks, and next step.
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Use pr-feedback-quality-gate for structured PR remediation with cross-review gating instead of editing files without checking PR state.
FAQ
What does pr-feedback-quality-gate inspect first?
pr-feedback-quality-gate inspects PR comments, reviews, mergeability, checks, branch state, and local worktree status first, ensuring unrelated local changes stay out of the pull request scope.
When should pr-feedback-quality-gate be invoked?
Invoke pr-feedback-quality-gate when a PR has review feedback, merge conflicts, pending checks, or needs monitored follow-up after a fix, including cross-review before committing changes.