Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

code-review-analyst

Étoiles3

Forks0

Mis à jour29 juin 2026 à 18:30

Scoped implementation-quality review. Use when Codex needs to review completed code changes for correctness, maintainability, codebase cohesion, edge cases, surface-level security, and architectural alignment. Use an RFC or plan as behavior context only; final RFC-to-code closure belongs to rfc-implementation-verifier.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

boris93

boris93/claude-setup

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Analystes en assurance qualité des logiciels et testeursProfessions informatiques et mathématiques·SOC 15-1253

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

name	code-review-analyst
description	Scoped implementation-quality review. Use when Codex needs to review completed code changes for correctness, maintainability, codebase cohesion, edge cases, surface-level security, and architectural alignment. Use an RFC or plan as behavior context only; final RFC-to-code closure belongs to rfc-implementation-verifier.

Code Review Analyst

Source

Read ../../../roles/code-review-analyst.md before acting. That file is the canonical, model-neutral role definition and the source of truth for this skill.

Also read only the needed supporting files:

../../../contracts/finding.md
../../../contracts/scope-block.md
../../../policies/synthesis.md
../../../policies/scope-discipline.md
../../../policies/contract-enforcement.md
../../../vocabulary.md
../../../contracts/code-change.md

If the relative paths are unavailable, try the same files under the configured Codex home ($CODEX_HOME when set, otherwise ~/.codex).

Procedure

Inspect the actual diff and all new files.
Anchor review on the scope block, synthesizing one only if the change was a direct dirty-tree edit without a prior plan.
Review implementation quality, local correctness, edge cases, maintainability, and codebase cohesion.
Cite exact file and line locations for findings.
Use RFCs or plans only to understand intended behavior; do not build the final RFC trace matrix.
Report introduced, actionable issues; route pre-existing adjacent issues according to the synthesis policy.

Plus depuis ce dépôt

même dépôt

rfc-implementation-verifier

boris93/claude-setup

Final RFC-to-code closure review. Use after code review convergence when an implementation was based on an RFC or plan and Codex must verify the final reviewed code implements all required behavior, avoids extra behavior, and documents deviations before commit or PR.

2026-06-293

review-convergence-analyst

boris93/claude-setup

Review-loop convergence diagnosis. Use when repeated code review or gating findings suggest unresolved architecture, requirement, invariant, ownership, or abstraction problems rather than independent bugs.

2026-06-203

gating-review

boris93/claude-setup

Strict dirty-tree gating review. Use when Codex needs to review only the uncommitted changes in the current repository, investigate the surrounding code, and emit tightly qualified findings in the repository's gating-review JSON style.

2026-05-283

rfc-minimizer

boris93/claude-setup

Subtractive plan minimality review. Use after RFC or plan review convergence to identify non-load-bearing content, inflated site lists, premature abstraction, or defensive structure not justified by the stated scope or prior blocking findings.

2026-05-283

rfc-red-team

boris93/claude-setup

Adversarial technical plan stress testing. Use when Codex needs to break an RFC or plan by constructing concrete failure scenarios, temporal risks, compositional blind spots, and operator or user behavior that a standard review may miss.

2026-05-283

rfc-reviewer

boris93/claude-setup

Structured technical RFC and plan review. Use when Codex needs to audit an RFC, implementation plan, or final pre-implementation sign-off for soundness, completeness, reuse, alternatives, and plan-altitude correctness.

2026-05-283

name	code-review-analyst
description	Scoped implementation-quality review. Use when Codex needs to review completed code changes for correctness, maintainability, codebase cohesion, edge cases, surface-level security, and architectural alignment. Use an RFC or plan as behavior context only; final RFC-to-code closure belongs to rfc-implementation-verifier.

Code Review Analyst

Source

Read ../../../roles/code-review-analyst.md before acting. That file is the canonical, model-neutral role definition and the source of truth for this skill.

Also read only the needed supporting files:

../../../contracts/finding.md
../../../contracts/scope-block.md
../../../policies/synthesis.md
../../../policies/scope-discipline.md
../../../policies/contract-enforcement.md
../../../vocabulary.md
../../../contracts/code-change.md

If the relative paths are unavailable, try the same files under the configured Codex home ($CODEX_HOME when set, otherwise ~/.codex).

Procedure

Inspect the actual diff and all new files.
Anchor review on the scope block, synthesizing one only if the change was a direct dirty-tree edit without a prior plan.
Review implementation quality, local correctness, edge cases, maintainability, and codebase cohesion.
Cite exact file and line locations for findings.
Use RFCs or plans only to understand intended behavior; do not build the final RFC trace matrix.
Report introduced, actionable issues; route pre-existing adjacent issues according to the synthesis policy.