Skip to main content
affpapa.org
RU EN
skill Claude Code CX Codex Cursor GitHub Copilot

pr-feedback-quality-gate — Claude Code skill: PR control

Skill for tracking pull request feedback, resolving merge conflicts, and validating fixes. Runs read-only cross-review before commit to catch issues in follow-up changes.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓ 
npx skills add nexu-io/open-design --skill pr-feedback-quality-gate -a claude-code
Open on GitHub

What pr-feedback-quality-gate does

This skill handles PR workflows at every stage: parsing reviewer comments, resolving merge conflicts, and validating fixes. It starts by inspecting PR state (comments, check status, branch, local worktree), then makes the minimal safe change while preserving the repository structure. Before each commit or push, it runs a read-only cross-review—the agent checks the diff without editing or git write permissions.

Under the hood: isolated worktree for dirty local checkouts, narrow validation checks (including pnpm guard and typechecks), and a status report with accepted blockers. The skill follows a monitoring cadence—frequent checks for active review or failing tests, every 12 hours for clean approved PRs, and daily observation after merge.

What it helps with

  • track reviewer feedback and keep comments in focus
  • resolve merge conflicts without breaking repository structure
  • validate fixes before push
  • get a read-only cross-review before commit
  • monitor PR through its lifecycle

Example prompts for the agent

  • My PR failed a check, debug the error and suggest a fix
  • The PR has two merge conflicts with main, help resolve them
  • A reviewer left a comment, validate and give a cross-review before I push

How to install pr-feedback-quality-gate

1Skills CLI (Vercel)

npx skills add nexu-io/open-design --skill pr-feedback-quality-gate -a claude-code

2Manually: put the files in place

~/.claude/skills/pr-feedback-quality-gate/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/pr-feedback-quality-gate/

From the same set106

The whole set →
ui-ux-pro-max nexu-io A discovery catalog entry for the UI/UX Pro Max skill in OpenDesign. It registers design system triggers so agents recognize interface usability requests. Claude Code CX Codex Cursor +1 5,400installs frontend-design nexu-io Skill for building frontend interfaces with considered typography, color and layout — from landing pages to dashboards. Claude Code CX Codex Cursor +1 4,800installs threejs nexu-io Guides the agent in building browser 3D scenes, materials, interactive controls, and post-processing with Three.js. Claude Code CX Codex Cursor +1 3,400installs creative-director nexu-io This skill takes a creative concept from brief to presentation and checks it on three axes. Use it for campaign ideas and creative critique. Claude Code CX Codex Cursor +1 3,400installs design-brief nexu-io Parses an I-Lang design brief into a concrete spec with palette, typography, density, and constraints. Eliminates ambiguity from phrases like "make it professional." Claude Code CX Codex Cursor +1 3,400installs apple-hig nexu-io Integrates Apple Human Interface Guidelines for iOS, macOS, visionOS, watchOS, and tvOS into your coding agent during planning. Claude Code CX Codex Cursor +1 3,200installs hatch-pet nexu-io Creates, validates, and packages 8×9 animated pet spritesheets for Codex. Use it when turning visual references or concept prompts into importable digital pet companions. Claude Code CX Codex Cursor +1 3,100installs design-md nexu-io Creates and maintains DESIGN.md with design direction, tokens, and visual rules. Useful when an agent needs one source of truth for a project’s design system. Claude Code CX Codex Cursor +1 3,100installs

Similar

context-mode-ops mksglu This skill coordinates GitHub work and releases through 10-20 dynamic subagents. Use it for issue triage, PR reviews, adapter checks, and branch sync. Claude Code CX Codex Cursor +1 1,700installs ce-commit EveryInc Automatically creates git commits with meaningful messages, splitting changes into logical chunks. Use when you need to save staged or unstaged files without pushing. Claude Code CX Codex Cursor +1 3,400installs ce-simplify-code EveryInc Simplifies code after implementation while keeping its behavior, and removes tests or comments with little value. Use it before review or for a repository audit. Claude Code CX Codex Cursor +1 3,400installs case-review zhaoxuya520 Audits a reverse engineering case package for handoff: verifies Evidence to Finding and Path traceability, checks artifact hash integrity, and generates a report without modifying the case. Claude Code CX Codex Cursor +1 926installs dry-refactoring kucherenko This skill automates refactoring of copy-paste clones found by jscpd. It guides you through extraction strategies—function, parameterization, module or class—and highlights which files to start with. Claude Code CX Codex Cursor +1 3,600installs how cursor Explores codebase architecture and runtime execution paths before you edit code. Helps determine module ownership, layering, and placement for new features. Claude Code CX Codex Cursor +1 5,900installs improve-codebase-architecture Matt Pocock This skill scans a codebase for architectural friction, then builds a visual HTML report with refactoring candidates. Use it before a deeper architecture review. Claude Code 1,163,035installs tdd Matt Pocock Guides the red-green TDD loop: ensures tests are written first, keep them at public interfaces, and avoid coupling to implementation details. Claude Code 1,141,062installs

Questions about pr-feedback-quality-gate

How do I install pr-feedback-quality-gate in Claude Code?

Run npx skills add nexu-io/open-design --skill pr-feedback-quality-gate -a claude-code. The skill will load from ~/.claude/skills/pr-feedback-quality-gate/SKILL.md.

What does pr-feedback-quality-gate do?

It tracks PR feedback, resolves merge conflicts, validates fixes, and runs cross-review before commit. Keeps follow-up changes safe and aligned with repository rules.

Why does it use an isolated worktree?

If your local checkout is dirty, behind remote, or in use by another agent, the skill creates a separate worktree for PR work to avoid mixing changes.

Source text

SKILL.md · Apache-2.0 
---
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

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.

© nexu-io · Apache-2.0 · nexu-io/open-design

See also

Project sponsors

Companies that keep this analytics open
Gold sponsor
Nutra.Club

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor