Evidence and findings
- 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.
nexu-io/open-design
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.
80Collecting
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "skills/pr-feedback-quality-gate"Automated source guideReview and auditStandard source
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Source-grounded review guide: 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.
npx skills add https://github.com/nexu-io/open-design --skill "skills/pr-feedback-quality-gate"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
280 source words · 3 usable sections
Review workflow
Read pr-feedback-quality-gate through these 3 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
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
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
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.
Review checklist
Verify each item before delivery
The source section “Workflow” has been checked.
The source section “Monitoring cadence” has been checked.
The source section “Report” has been checked.
Source output checked: 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.
Choose a different workflow
When another Skill is the better fit
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
A separate implementation from Jeffallan/claude-skills; compare its source, maintenance signals, and permission requirements.
Open source detaildmux-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.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailswiftui-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.
A separate implementation from dpearson2699/swift-ios-skills; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
What does the pr-feedback-quality-gate source document cover?
Use this when a PR has review feedback, merge conflicts, pending checks, or needs a monitored follow-up after a fix.
How do I install pr-feedback-quality-gate?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/pr-feedback-quality-gate". Inspect the command and pinned source before running it.
Repository stars
82,073
Repository forks
9,485
Quality
80/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation20/30
Specificity18/25
Maintenance20/20
Trust signals22/25
Compare before choosing
Related Agent Skills and source variants
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
code-reviewer by jeffallan
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
dmux-workflows by affaan-m
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.
swiftui-performance by dpearson2699
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.
dmux-workflows by affaan-m
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.
postmortem-writing by wshobson
Write effective blameless postmortems with root cause analysis, timelines, and action items. Use when conducting incident reviews, writing postmortem documents, or improving incident response processes.
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min
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.
- Source repo
- nexu-io/open-design
- Skill path
- skills/pr-feedback-quality-gate/SKILL.md
- Commit SHA
- 89d6d4ef21ba
- Repository license
- Apache-2.0
- Data collected