pr-feedback-quality-gate
nexu-io/open-design
Track PR feedback, resolve conflicts, validate fixes, and cross-review before committing changes.
What is pr-feedback-quality-gate?
A workflow skill for safely managing pull request review comments, merge conflicts, and validation gates. Use it when a PR has pending feedback, needs conflict resolution, or requires monitored follow-up after fixes.
- Inspect PR state including comments, reviews, mergeability, checks, and branch status
- Use isolated worktrees for conflict resolution when the main checkout is dirty or in use
- Run narrow validation and repository-required quality gates (e.g., pnpm guard)
- Perform read-only cross-review of staged diffs before committing or pushing
- Track and report PR state, actions taken, validation results, and remaining risks
- Monitor PR cadence based on status: active review, approved waiting, or merged
How to install pr-feedback-quality-gate
npx skills add https://github.com/nexu-io/open-design --skill pr-feedback-quality-gateHow to use pr-feedback-quality-gate
- 1.Inspect the PR state: comments, reviews, mergeability, checks, and branch status
- 2.Create an isolated worktree if the main checkout is dirty or in use
- 3.Make the smallest safe fix that addresses the feedback or conflict
- 4.Run narrow validation first, then repository-required gates (e.g., pnpm guard)
- 5.Run a read-only cross-review of the staged diff; forbid file edits and git write commands
- 6.Accept only findings grounded in the diff, rules, or validation; reject style preferences that conflict with safety
- 7.Fix any accepted blockers, rerun validation, and repeat the review if needed
- 8.Commit and push only after validation passes and no accepted blockers remain
Use cases
- Resolving merge conflicts in a PR while keeping local changes isolated
- Fixing review comments and validating the changes against CI gates before pushing
- Cross-reviewing a proposed fix to catch issues before committing
- Monitoring a merged PR for CI failures or regression signals
- Managing follow-up changes to a PR that failed validation checks
- Developers managing pull requests with review feedback
- Teams enforcing code quality gates and validation workflows
- Engineers resolving merge conflicts in collaborative branches
- Code reviewers needing structured cross-review before merge
pr-feedback-quality-gate FAQ
Use an isolated worktree when the main checkout is dirty, behind remote, or being used by another agent. This keeps unrelated local changes out of the PR.
Run narrow validation first (specific to changed files), then repository-required gates. For this repo, always include pnpm guard; add package typechecks, builds, or tests when touched files require them.
Before committing or pushing, run a read-only cross-review of the staged or proposed diff. This is evidence-based feedback; accept only findings grounded in the diff, repository rules, user goal, or validation results.
Check frequently for active reviews or failing checks; check every 12 hours for approved PRs waiting to merge; check daily for merged PRs to watch for CI, release, or regression signals.
Stop making code changes after the PR is merged unless explicitly asked. Switch to lightweight observation for CI, release, or regression signals.
Full instructions (SKILL.md)
Source of truth, from nexu-io/open-design.
name: pr-feedback-quality-gate description: | Safely track pull request feedback, resolve review comments or merge conflicts, validate fixes, and use a read-only cross-review before committing or pushing follow-up changes. triggers:
- "PR feedback"
- "review comments"
- "merge conflicts"
- "cross-review"
- "Claude CLI review"
- "monitor PR" od: mode: utility
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
- Inspect PR state first: comments, reviews, mergeability, checks, branch, and local worktree status. Keep unrelated local changes out of the PR.
- Use an isolated worktree for review fixes or conflict resolution when the main checkout is dirty, behind remote, or being used by another agent.
- Make the smallest safe fix. Preserve the original bug invariant and any
newer upstream structure introduced by
main. - 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. - 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.
- 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.
- 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
More from nexu-io/open-design and the wider catalog.
redesign-existing-projects
Audit and upgrade existing websites to premium quality without breaking functionality.
reference-design-contract
Turn design references into a reusable DESIGN.md contract before prototyping or generation.
release-notes-one-pager
Generate a single-page HTML release notes document with highlights, changes, and upgrade guidance.
remotion
Programmatic video creation with React for branded content, social cuts, and motion graphics.
replicate
Discover, compare, and run AI models via Replicate's API for image, audio, and video generation.
research-decision-room
Turn research notes into an evidence-backed decision room with themes, confidence scores, and experiment queues.