Run any Skill in Manus with one click

$pwd:

pr-feedback-quality-gate

Name: Pr Feedback Quality Gate
Author: nexu-io

// 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.

Run Skill in Manus

$ git log --oneline --stat

stars:56,027

forks:6,338

updated:May 30, 2026 at 04:44

SKILL.md

readonly

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

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.

related-skills.json

same repository

export-download-debugging.md

from "nexu-io/open-design"

Diagnose and fix browser, preview, or Electron export/download failures, especially image export issues involving Save As, Blob/Data URLs, the File System Access API, createWritable failures, and 0 KB files.

2026-05-3056.0k

simple-deck.md

from "nexu-io/open-design"

Single-file horizontal-swipe HTML deck. Built by copying the seed `assets/template.html` (which carries the proven 5-rule iframe nav script) and pasting slide layouts from `references/layouts.md`. Pitch decks, product overviews, study material — when you don't need the magazine aesthetic of `magazine-web-ppt`.

2026-05-2956.0k

simple-deck.md

from "nexu-io/open-design"

2026-05-2956.0k

od-contribute.md

from "nexu-io/open-design"

One-click contribution flow for Open Design (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship my OD skill, ship my OD design system, translate OD docs, report an OD bug, od-contribute.

2026-05-2956.0k

token-map.md

from "nexu-io/open-design"

Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.

2026-05-2956.0k

web-prototype.md

from "nexu-io/open-design"

General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.

2026-05-2956.0k

package.json

"author": "nexu-io"

"repository": "nexu-io/open-design"

View GitHub Repository View Creator Repositories

$ install --global

$ download --local

Run Skill in Manus

$ useful --forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

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.

pr-feedback-quality-gate

PR Feedback Quality Gate

Workflow

Monitoring cadence

Report

More from this repository

PR Feedback Quality Gate

Workflow

Monitoring cadence

Report

More from this repository