Source profileQuality 80/100

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
91,167
Declared platforms
0
Static risk flags
0
Last source update
2026-08-25
Source checked
2026-08-25
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSourceFAQ

Decision brief

What it does: where it fits

Use this when a PR has review feedback, merge conflicts, pending checks, or needs a monitored follow-up after a fix.

Best for

    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

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    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.

    Source-detected install commandSource
    npx skills add https://github.com/nexu-io/open-design --skill "skills/pr-feedback-quality-gate"
    Safe inspection promptEditorial

    Inspect the Agent Skill "pr-feedback-quality-gate" from https://github.com/nexu-io/open-design/blob/edfa6b5f447e95cb120eae030f03baba00dc34de/skills/pr-feedback-quality-gate/SKILL.md at commit edfa6b5f447e95cb120eae030f03baba00dc34de. 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

    1. 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
    2. 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
    3. 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

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score80/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars91,167SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated 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
    edfa6b5f447e95cb120eae030f03baba00dc34de
    License
    Apache-2.0
    Collected
    2026-08-25
    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

    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.

    Frequently asked questions

    What to verify before installation and use

    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.

    Alternatives

    Compare before choosing

    Computed 9858

    magnus919/agent-skills

    software-architecture-analysis

    Use this skill to reverse-engineer an existing software system, map its architecture, data flow, privacy posture, coupling, quality characteristics, and feature surface, then produce an evidence-grounded clean-room design document, PRD, or migration plan under new constraints. Use for codebase archaeology, implicit contract extraction, architecture health assessment, or decomposition-readiness analysis. Do not use for greenfield architecture design, direct code review, bug hunting, security audi

    2026-08-240 platforms
    Computed 9721

    VincentChuWaiChow/vanguard-frontier-agentic

    salesforce-apex-log-analyzer-skill

    Retrieves and analyzes Apex debug logs from a connected Salesforce org to identify governor-limit hits, SOQL N+1 patterns, unhandled exceptions, and async job failures. T1 read-only runtime — retrieves logs only, never executes code or mutates data. TRIGGER when: user asks to analyze an Apex log, debug a trigger failure, diagnose a governor limit hit, interpret a stack trace from a Salesforce org, or review a DEBUG log for performance issues. Trigger phrases: analyze apex log, debug this trigger

    2026-08-240 platforms
    Computed 9691,519

    ruvnet/RuView

    github-code-review

    Comprehensive GitHub code review with AI-powered swarm coordination

    2026-08-251 platforms
    Computed 955,241

    dotnet/skills

    grade-tests

    Grades a specified set of test methods individually and produces a concise table mapping each test (fully-qualified name) to a letter grade (A–F), a score band, and a one-line note — designed to be posted as a PR comment. Use when the caller wants per-test feedback on a curated list of methods (for example, the new or modified tests in a pull request), not a suite-wide audit. Polyglot: .NET, Python, TS/JS, Java, Go, Ruby, Rust, Swift, Kotlin, PowerShell, C++. Input is a list of test methods (or

    2026-08-240 platforms