phenomenal-review

Adversarial correctness and contract review of a git diff via docs/agent/phenomenal-review.md (split-context reviewer stance; optional multi-pass). Produces structured findings and checkable follow-up tasks under docs/ (not chat-only). Use when the user asks for a phenomenal review, deep review, adversarial review, contract review, correctness review of local/branch/PR changes, or wants residual work filed into plan docs. Do not use for pre-ship fix loops, maintainability/code-judo audits, or implementing fixes unless the user explicitly asks to harden after the review.

Ir para a instalação

Repositório: scoizzle/Poly
Última atividade na origem: 31 de julho de 2026 às 02:44
Idioma detectado do SKILL.md: inglês
Estrelas: 5
Forks: 1

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.

npx skills add https://github.com/scoizzle/Poly --skill phenomenal-review

O comando permanece em uma só linha. Role horizontalmente para revisá-lo antes de copiar.

Prefere uma cópia local? Baixe os arquivos disponíveis atualmente no SkillsMP.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

SKILL.md

Instruções da origem · Visualização somente leitura

Voltar à pesquisa Voltar à instalação

Phenomenal review (Copilot / Agent Skills wrapper)

This skill is a thin adapter. The full protocol is tool-agnostic and lives in the repository:

docs/agent/phenomenal-review.md

Also see: docs/agent/README.md.

Instructions

Open and follow docs/agent/phenomenal-review.md completely. Do not substitute a lighter checklist.

Determine the review target (default: uncommitted local changes; or branch / PR / paths if specified) and mode (standard or multi).

Adversarial stance: assume the code is wrong; reviewer is not implementer; prefer diff-first. If this session wrote the code, use multi-pass with a fresh context and the Pass B template (docs/agent/phenomenal-review.md §3.7.1).

Collect the diff, trace producer/consumer call graphs, hunt fail-closed and contract bugs (sibling-path drift, reachability before severity, primary-evidence counts, invariant comments as checklists, same-shape-different-meaning, oracle weakening), audit tests and plan honesty — as the protocol specifies.

Do not modify production or test code unless the user explicitly requests a harden/pre-ship pass after the review.

Required deliverables:

A structured review markdown file under docs/ (suite path or docs/agent/reviews/YYYY-MM-DD-<slug>.md).
Checkable follow-up tasks under docs/ (including process fixes when bug classes recur). Chat alone is not enough.

End with a short user report: verdict, bug/suggestion/nit counts, paths to the two docs, top issues.

Related (do not merge)

Always-on repo rules: AGENTS.md / Agents.md, .github/copilot-instructions.md

Pre-ship fix gate: docs/plans/v2-to-v3/simple-agent-tasks/pr1-uncommitted-review-gate.md

Maintainability audits: separate skill if present; this skill is correctness/contracts first