skills.rest
JMTassy
JMTassyCOMMUNITY
Explore all skills by this author →
GitHub

feynman/peer_review

Generate a pending REVIEW_V1 payload for HELEN artifacts awaiting witness validation.

Updated Apr 4, 2026
Search Tags:#feedback#verification#governance#peer-review#artifact-review#HELEN
One-click install
npx skills add https://github.com/JMTassy/helen-conquest --skill feynman-peer-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feynman/peer_review
Source: https://github.com/JMTassy/helen-conquest/tree/main/oracle_town/skills/feynman/peer_review
Command: npx skills add https://github.com/JMTassy/helen-conquest --skill feynman-peer-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tough-but-constructive peer review of any HELEN artifact (manifesto, claim, draft, code change). Wraps the Feynman /review workflow under HELEN's K2 / Rule 3 ("Editor cannot approve own work"). Use when the user asks for a review, critique, or wants to surface weaknesses before SHIP.

Core Features & Use Cases

  • Independent review of artifacts to surface weaknesses before shipping.
  • Produces a pending REVIEW_V1 payload that requires an external witness before it becomes binding.
  • Ensures compliance with HELEN conditions: reviewer ≠ proposer, termination via SHIP/ABORT, and no direct binding.

Quick Start

Submit a REVIEW_REQUEST for the target artifact to trigger a pending REVIEW_V1 review.

Frequently Asked Questions about feynman/peer_review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an independent peer review for a code change before shipping?▼

Independent peer review for a code change is triggered by submitting a REVIEW_REQUEST, which produces a structured REVIEW_V1 payload that surfaces weaknesses before shipping. This enforces the reviewer ≠ proposer rule to ensure auditability.

What is a pending REVIEW_V1 payload in artifact governance?▼

A pending REVIEW_V1 payload is a structured review output for HELEN artifacts that surfaces weaknesses but awaits external witness validation before becoming binding. It ensures no direct binding occurs without independent verification.

Can I review my own artifact claims under HELEN governance rules?▼

You cannot review your own artifact claims because HELEN's K2 Rule 3 enforces that the editor cannot approve their own work. The peer review workflow strictly maintains a reviewer ≠ proposer separation.

How do I terminate a peer review workflow for a draft artifact?▼

Terminating a peer review workflow for a draft artifact requires a SHIP or ABORT signal to ensure auditability. The process evaluates surfaced weaknesses and concludes with one of these explicit termination states.

What types of artifacts can be critiqued using an independent peer review process?▼

Independent peer review can critique manifests, claims, drafts, and code changes when a user requests feedback before shipping. The scope covers any HELEN artifact requiring weakness verification.

Why does my artifact review require an external witness before it becomes binding?▼

Artifact review requires an external witness because the peer review process produces a pending claim that prevents direct binding. This governance mechanism ensures independent validation before any artifact is officially approved.

Related Skills

Explore More Software Engineering Skills→
DigiBanks99DigiBanks99
1

mcp-builder

Design MCP servers for LLMs to call external services via defined tools.

Community
Advanced
tkerseytkersey
66

ship

Confirm validation signals, summarize proof, and open a non-merged PR via gh.

Community
Intermediate
pedapudipedapudi
4

zicato-design-proposer

Configure zicato's proposer agent for grounded harness mutation experiments.

Community
Advanced
djnsty23djnsty23
2

ship

Orchestrate deployment validation with pre-flight checks, security scans, and rollback support.

Community
Advanced