一键在 Manus 中运行任何 Skill

final-code-review

星标1

分支0

更新时间2026年7月6日 12:32

Use when the user wants a final technical gate on an open PR or MR after peer review — architecture boundaries, security, and acceptance-criteria coverage against .agency/work/{epic}/tasks.md. Do NOT use for pre-PR peer review (code-review), business stakeholder sign-off (validate), or implementation (implement).

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

carinyaparc

carinyaparc/digital-agency

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Final code review

Post-MR final gate: architecture, security, and technical AC coverage. The MR is open and CI is expected green. This is not defect-finding peer review — that happens before the MR opens.

Follow prompts/run.prompt.md.

Pass branch, PR, or MR URL after the skill name.

同仓库更多 Skills

同仓库

setup

carinyaparc/digital-agency

Web development practice setup interview — detects or creates .agency/target.json binding, reads instance profile from `/agency-hub:setup`, interviews tech stack, deployment platform, connectors, and persona preference (six engineering personas vs merged), writes practice profile. Use on first install after `/agency-hub:setup`, when the user says "set up web development" or "bind target repo", or to redo engineering defaults only.

2026-07-071

ralph

carinyaparc/digital-agency

Use when the user wants to run a Ralph loop: an autonomous, self-referential delivery loop that drives a whole epic through implement, code review, fix, UX review, validate, commit, and merge request, one task per iteration, until a completion promise is emitted (ralph setup, ralph start), or to inspect or stop a running loop (ralph status, ralph cancel). Also supports simple ad-hoc loops that repeat a single prompt until done. Do NOT use to implement a single task once (implement), review a diff (code-review), or sign off an epic (validate) — the loop orchestrates those skills.

2026-07-071

ux-design-review

carinyaparc/digital-agency

Use when the user wants a UX/design review of implemented UI — frontend components, pages, or flows — against the design source of truth (Figma via MCP, mockups, tokens, or style guide, whatever the repo provides), covering design fidelity, accessibility (WCAG 2.2 AA), interaction states, responsiveness, and design-system conformity; or to address UX review findings (ux-design-review fix, optionally scoped to an action tier). Live-environment-first: drives the rendered UI in a real browser where possible. Works with any framework or design tooling. Do NOT use for code correctness/security review (code-review), to review a design.md document (design), or to implement features (implement).

2026-07-071

merge-request-review

carinyaparc/digital-agency

Use when the user is the reviewer of a merge request or pull request and wants it reviewed and the verdict published to the provider — inline comments on the right lines, threads resolved or replied to, and an approve / request-changes / comment decision. Handles first reviews and re-review rounds after the author pushes. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise. Do NOT use to review your own working diff before opening an MR (code-review), to open or babysit an MR (merge-request), or to implement changes (implement).

2026-07-071

merge-request

carinyaparc/digital-agency

Use when the user wants to open a merge request or pull request for the current branch (merge-request create — the default — with a generated title, description, labels, and reviewer suggestions), or to babysit an open MR/PR to a merge-ready state (merge-request babysit) by watching CI, review comments, and merge conflicts. Works with any codebase and any git provider — GitHub, GitLab, or Bitbucket — using MCP tools where available, provider CLIs otherwise, and plain git as a last resort. Do NOT use to review code or an MR as its reviewer (code-review, merge-request-review) or to implement changes (implement).

2026-07-071

code-review

carinyaparc/digital-agency

Use when the user wants a code review of a branch, PR, or diff against its acceptance criteria and declared scope (whatever form they take in this repo), or to address review feedback without changing behaviour (code-review fix, optionally scoped to a blocking or warning action tier). Works with any language, delivery process, or issue tracker. Do NOT use to implement code, sign off completion of a larger body of work, or review rendered UI/UX (design fidelity, accessibility — use ux-design-review).

2026-07-071

name	final-code-review
description	Use when the user wants a final technical gate on an open PR or MR after peer review — architecture boundaries, security, and acceptance-criteria coverage against .agency/work/{epic}/tasks.md. Do NOT use for pre-PR peer review (code-review), business stakeholder sign-off (validate), or implementation (implement).
license	MIT
allowed-tools	["Read","Glob","Grep","Shell"]
argument-hint	[branch-or-pr-or-mr-url]

Final code review

Post-MR final gate: architecture, security, and technical AC coverage. The MR is open and CI is expected green. This is not defect-finding peer review — that happens before the MR opens.

Follow prompts/run.prompt.md.

Pass branch, PR, or MR URL after the skill name.