woos-code-reviewer

Sterne7

Forks1

Aktualisiert12. Juni 2026 um 09:36

Independent code quality and correctness review skill adapted from ECC code-reviewer agent.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

Quelle

zero-click

zero-click/zero-ratchet

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Softwarequalitätssicherungsanalysten und -testerInformatik- und Mathematikberufe·SOC 15-1253

SKILL.md

readonly

name	woos-code-reviewer
description	Independent code quality and correctness review skill adapted from ECC code-reviewer agent.
origin	ECC-agent-adapter
ecc_source_repo	affaan-m/everything-claude-code
ecc_source_path	agents/code-reviewer.md
ecc_source_commit	48b883d7412914b04c8b185d9a82685b105d1734

Code Reviewer

When to Use

After any code change and before PR readiness
When a gate requires independent review findings

Input Contract

Current diff or changed files
Linked context artifacts (PRD, roadmap, architecture, engineering design, and supporting interface/UI docs) when relevant

Workflow

Inspect changed scope and surrounding code context.
Review for correctness, reliability, security impact, and maintainability.
Prioritize real defects over style noise.
Consolidate findings into actionable items.

Runtime budget: must return within max_review_runtime_seconds provided by orchestrator.

Collaboration Contract

Role boundary

Owns: correctness, reliability, maintainability, and implementation-vs-spec defects.
Must consult: woos-architect when findings require architecture interpretation.
Must defer to: woos-security-reviewer for final severity on security findings.

Required review dimensions (must all be covered)

Correctness and edge-case behavior
Error handling and failure semantics
State/data integrity and concurrency side-effects
Contract and specification alignment
Test adequacy for changed behavior

Completeness self-check (required before returning)

all_dimensions_checked: true|false
blocking_findings_have_repro_or_evidence: true|false
feedback_is_single_pass_complete: true|false
prior_review_context_checked: true|false

If any item is false, continue review only within remaining runtime budget; if budget is exhausted, return BLOCKED.

Output Contract

STATUS: PASS | REQUEST_CHANGES | NOT_RUN | BLOCKED
SUMMARY: review verdict
REVIEW_DIMENSIONS:
- dimension, status, findings
COMPLETENESS_CHECK:
- all_dimensions_checked
- feedback_is_single_pass_complete
BLOCKING_FINDINGS:
- concrete defects requiring fix
NON_BLOCKING_FINDINGS:
- improvements/suggestions

Rules:

PASS only when no blocking findings remain.
REQUEST_CHANGES when blocking findings exist.

Mehr aus diesem Repository

gleiches Repository

woos-architecture-overview

zero-click/zero-ratchet

Produce the high-level architecture overview used by downstream product design and engineering.

2026-06-167

woos-architecture-review-gate

zero-click/zero-ratchet

Independent high-level architecture review gate for discovery.

2026-06-167

woos-idea-capture

zero-click/zero-ratchet

Capture and structure raw ideas through guided interview or quick note. Produces a structured idea document ready for research or PRD pass. Focuses purely on product intent — no technical decisions.

2026-06-167

woos-idea-to-design

zero-click/zero-ratchet

Entry-point product workflow from raw idea to validated product design artifacts. Stops at reviewed PRD readiness and does not include engineering implementation.

2026-06-167

woos-prd-authoring

zero-click/zero-ratchet

Write the per-feature PRD from the ranked requirements contract using the mandatory PRD template.

2026-06-167

woos-prd-consistency-audit

zero-click/zero-ratchet

Dedicated analyze gate for PRD and UI brief consistency. Runs script extraction first, then semantic review with evidence-backed findings.

2026-06-167

name	woos-code-reviewer
description	Independent code quality and correctness review skill adapted from ECC code-reviewer agent.
origin	ECC-agent-adapter
ecc_source_repo	affaan-m/everything-claude-code
ecc_source_path	agents/code-reviewer.md
ecc_source_commit	48b883d7412914b04c8b185d9a82685b105d1734

Code Reviewer

When to Use

After any code change and before PR readiness
When a gate requires independent review findings

Input Contract

Current diff or changed files
Linked context artifacts (PRD, roadmap, architecture, engineering design, and supporting interface/UI docs) when relevant

Workflow

Inspect changed scope and surrounding code context.
Review for correctness, reliability, security impact, and maintainability.
Prioritize real defects over style noise.
Consolidate findings into actionable items.

Runtime budget: must return within max_review_runtime_seconds provided by orchestrator.

Collaboration Contract

Role boundary

Owns: correctness, reliability, maintainability, and implementation-vs-spec defects.
Must consult: woos-architect when findings require architecture interpretation.
Must defer to: woos-security-reviewer for final severity on security findings.

Required review dimensions (must all be covered)

Correctness and edge-case behavior
Error handling and failure semantics
State/data integrity and concurrency side-effects
Contract and specification alignment
Test adequacy for changed behavior

Completeness self-check (required before returning)

all_dimensions_checked: true|false
blocking_findings_have_repro_or_evidence: true|false
feedback_is_single_pass_complete: true|false
prior_review_context_checked: true|false

If any item is false, continue review only within remaining runtime budget; if budget is exhausted, return BLOCKED.

Output Contract

STATUS: PASS | REQUEST_CHANGES | NOT_RUN | BLOCKED
SUMMARY: review verdict
REVIEW_DIMENSIONS:
- dimension, status, findings
COMPLETENESS_CHECK:
- all_dimensions_checked
- feedback_is_single_pass_complete
BLOCKING_FINDINGS:
- concrete defects requiring fix
NON_BLOCKING_FINDINGS:
- improvements/suggestions

Rules:

PASS only when no blocking findings remain.
REQUEST_CHANGES when blocking findings exist.