nexu-io/open-design/skills/pr-feedback-quality-gate/SKILL.md
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.
- Source repository stars
- 82,073
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
Use this when a PR has review feedback, merge conflicts, pending checks, or needs a monitored follow-up after a fix.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/nexu-io/open-design --skill "skills/pr-feedback-quality-gate"Inspect the Agent Skill "pr-feedback-quality-gate" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/pr-feedback-quality-gate/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
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…
Inspect PR state first: comments, reviews, mergeability, checks, branch, andUse an isolated worktree for review fixes or conflict resolution when theMake the smallest safe fix. Preserve the original bug invariant and any - 02
Monitoring cadence
Active review or failing checks: check often enough to unblock quickly.
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 - 03
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.
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.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 80/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 82,073 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- nexu-io/open-design
- Skill path
- skills/pr-feedback-quality-gate/SKILL.md
- Commit
- 89d6d4ef21baf80f871595abdf6f7de6e941dd44
- License
- Apache-2.0
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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.
Alternatives
Compare before choosing
Jeffallan/claude-skills
code-reviewer
Analyzes code diffs and files to identify bugs, security vulnerabilities (SQL injection, XSS, insecure deserialization), code smells, N+1 queries, naming issues, and architectural concerns, then produces a structured review report with prioritized, actionable feedback. Use when reviewing pull requests, conducting code quality audits, identifying refactoring opportunities, or checking for security issues. Invoke for PR reviews, code quality checks, refactoring suggestions, review code, code quali
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.
dpearson2699/swift-ios-skills
swiftui-performance
Profile, diagnose, and remediate SwiftUI runtime performance using code review, Instruments, and repeatable measurements. Use when a SwiftUI screen renders slowly, scrolling or animations hitch, view bodies update excessively, list identity churns, layout work spikes, or broad Observation dependencies raise CPU cost. Covers evidence-based triage, SwiftUI Instruments lanes, lazy-container guardrails, state lifetime, and before/after verification.
affaan-m/ECC
dmux-workflows
Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.