Pr feedback quality gate

Skill nexu-io/open-design/skills/pr-feedback-quality-gate

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.From its SKILL.md

Install

npx -y skills add nexu-io/open-design --skill pr-feedback-quality-gate

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.2 KB, 405 tokens by cl100k_base, as published. Nobody here has run it

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.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most quality gates skills give in 405 tokens

Counted across 1,524 of the 2,830 authors here whose files we hold, read 2026-09-06

Read full output and check exit codein 45 of 1524, across 40 files
Verify output confirms the claimin 44 of 1524, across 39 files
Identify the command that proves the claimin 43 of 1524, across 39 files
Execute the full verification commandin 36 of 1524, across 30 files
Produce a verification reportin 34 of 1524, across 18 files
Review git diff changesin 30 of 1524, across 16 files
Fix build failures immediatelyin 29 of 1524, across 9 files
Group findings by severityin 28 of 1524
State claim only with evidencein 27 of 1524, across 22 files
Verify regression tests with red-green cyclein 26 of 1524, across 22 files
Run the full test suitein 26 of 1524, across 25 files
Run test suite with coveragein 25 of 1524, across 10 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.