pr-feedback-quality-gate

Monitor pull request feedback and validate code changes against repository quality standards.

93.2k|10.8k|Updated Apr 28, 2026

Search Tags:#Git #merge conflict #quality gate #Automation #Code review #Pull request

One-click install

npx skills add https://github.com/nexu-io/open-design --skill pr-feedback-quality-gate

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: pr-feedback-quality-gate
Source: https://github.com/nexu-io/open-design/tree/main/skills/pr-feedback-quality-gate
Command: npx skills add https://github.com/nexu-io/open-design --skill pr-feedback-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the friction of managing pull request feedback, merge conflicts, and pending checks, ensuring that follow-up changes are safe and compliant with repository rules.

Core Features & Use Cases

PR State Inspection: Automatically analyzes comments, reviews, mergeability, and local worktree status.
Isolated Conflict Resolution: Manages fixes in isolated worktrees to prevent interference with main checkouts.
Quality Gate Validation: Enforces repository-required checks like pnpm guard, typechecks, and tests before committing changes.
Use Case: When a PR has multiple review comments and merge conflicts, use this Skill to systematically resolve issues, run necessary validations, and perform a read-only cross-review before pushing updates.

Quick Start

Use the pr-feedback-quality-gate skill to inspect the current pull request and resolve pending review comments.

Frequently Asked Questions about pr-feedback-quality-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I resolve merge conflicts using this skill?▼

The skill guides you to use an isolated worktree for conflict resolution, ensuring the main checkout remains clean. It then requires you to run narrow validation and repository-required gates before committing the fix.

What is the purpose of the read-only cross-review?▼

The cross-review acts as a final safety check to verify that proposed changes align with repository rules and user goals. It forbids file edits and git write commands to ensure the review remains objective and evidence-based.

Does this skill support automated PR merging?▼

No, this skill focuses on the quality gate and feedback resolution process. It stops after validation passes and there are no accepted blockers, leaving the final merge action to the user or CI system.

When should I use this skill for PR monitoring?▼

Use it during active review cycles to unblock progress, every 12 hours for approved PRs waiting for merge, and daily for lightweight observation of merged PRs to detect regression signals.