woos-review-context

Stars4

Forks0

UpdatedMay 12, 2026 at 15:51

Maintain cumulative cross-gate review context so reviewers build on prior findings instead of restarting from zero.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

zero-click

zero-click/zero-prd-to-pr

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	woos-review-context
description	Maintain cumulative cross-gate review context so reviewers build on prior findings instead of restarting from zero.
version	1.5.0
author	Hermes Profile
license	MIT

Woos Review Context

Purpose

Provide a shared, cumulative review memory across PRD/design/code/security gates.

Required Behavior

Load prior review context before invoking any reviewer.
Pass unresolved prior findings into the current review prompt.
Require explicit resolution status for each prior blocking finding.
Persist new findings with ownership, severity, and target artifact.
Preserve finding identity across gates and rounds; do not emit duplicate findings with new IDs.

Persistence Contract (mandatory)

Review context MUST be stored on disk (not only in transient prompt state).
Canonical runtime root: <workspace_root>/hep.
Default path: <workspace_root>/hep/review-context/<run_id>.yaml.
review-context/ directory is created lazily by orchestrator/runtime when missing.
For gated runs, run_id is mandatory. If unavailable, return BLOCKED.
Every review gate update MUST overwrite the same run file and append a new gate_entry.
Reviewer prompts MUST include a concise summary loaded from this file.

Review Context Schema

run_id
artifact_id
gate
reviewers
new_findings
resolved_findings
carry_forward_findings
finding_id
first_seen_gate
status (open | resolved | reopened)
resolved_in_gate
supersedes
coverage_summary
completeness_check
context_file_path
gate_entries

Output Contract

status: PASS | REQUEST_CHANGES | BLOCKED
review_context_loaded: boolean
review_context_updated: boolean
context_file_path
unresolved_findings
resolved_findings
carry_forward_findings

Machine-Readable Enforcement Output (required)

{
  "enforcement": {
    "required_invocations": ["woos-review-context"],
    "actually_invoked": ["woos-review-context"],
    "missing_invocations": [],
    "context_file_written": true,
    "invocation_evidence": [
      {
        "skill": "woos-review-context",
        "invoked_at": "2026-05-12T22:00:00Z",
        "artifact_ref": "<workspace_root>/hep/review-context/<run_id>.yaml",
        "output_digest": "sha256:..."
      }
    ],
    "finding_identity_checks_passed": true,
    "completeness_passed": true
  }
}

Missing invocation_evidence MUST return BLOCKED.

More from this repository

same repository

woos-ui-design-brief

zero-click/zero-prd-to-pr

Transform product requirements into a focused UI/UX design brief with screens, flows, visual direction, and optional image-generation concepts. Bridge between product thinking and implementation.

2026-06-124

woos-development-workflow

zero-click/zero-prd-to-pr

Stage 3 of idea-to-delivery: gated engineering workflow that receives PRD, roadmap, and architecture inputs, decomposes into stories, and executes with TDD, traceability, and review gates.

2026-06-124

woos-product-planner

zero-click/zero-prd-to-pr

Planning and decomposition review skill adapted from ECC planner agent. Covers story-set review (Gate 2) and planning consults for upstream skills. PRD-quality review is NOT in scope — that is owned by `woos-product-prd-review-gate`.

2026-06-124

woos-story-decomposition

zero-click/zero-prd-to-pr

Produce a lean story plan (table) for the Gate 3 execution loop — execution order plus diff scope per story. PRD AC is the spec; tests are the verification. No per-story prose documents.

2026-06-124

woos-agent-decision

zero-click/zero-prd-to-pr

Resolve multi-agent review conflicts with explicit authority matrix, evidence weighting, and escalation criteria.

2026-06-124

woos-architect

zero-click/zero-prd-to-pr

Architecture review and design skill adapted from ECC architect agent. Use for design validation, trade-off analysis, and system-level decisions.

2026-06-124

Woos Review Context

Purpose

Provide a shared, cumulative review memory across PRD/design/code/security gates.

Required Behavior

Load prior review context before invoking any reviewer.

Pass unresolved prior findings into the current review prompt.

Require explicit resolution status for each prior blocking finding.

Persist new findings with ownership, severity, and target artifact.

Preserve finding identity across gates and rounds; do not emit duplicate findings with new IDs.

Persistence Contract (mandatory)

Review context MUST be stored on disk (not only in transient prompt state).

Canonical runtime root: <workspace_root>/hep.

Default path: <workspace_root>/hep/review-context/<run_id>.yaml.

review-context/ directory is created lazily by orchestrator/runtime when missing.

For gated runs, run_id is mandatory. If unavailable, return BLOCKED.

Every review gate update MUST overwrite the same run file and append a new gate_entry.

Reviewer prompts MUST include a concise summary loaded from this file.

Review Context Schema

run_id

artifact_id

gate

reviewers

new_findings

resolved_findings

carry_forward_findings

finding_id

first_seen_gate

status (open | resolved | reopened)

resolved_in_gate

supersedes

coverage_summary

completeness_check

context_file_path

gate_entries

Output Contract

status: PASS | REQUEST_CHANGES | BLOCKED

review_context_loaded: boolean

review_context_updated: boolean

context_file_path

unresolved_findings

resolved_findings

carry_forward_findings

Machine-Readable Enforcement Output (required)

{ "enforcement": { "required_invocations": ["woos-review-context"], "actually_invoked": ["woos-review-context"], "missing_invocations": [], "context_file_written": true, "invocation_evidence": [ { "skill": "woos-review-context", "invoked_at": "2026-05-12T22:00:00Z", "artifact_ref": "<workspace_root>/hep/review-context/<run_id>.yaml", "output_digest": "sha256:..." } ], "finding_identity_checks_passed": true, "completeness_passed": true } }

Missing invocation_evidence MUST return BLOCKED.