Menu
Use when accepted findings require bounded repair changes and a structured repair summary.
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ê.
Baseado na classificação ocupacional SOC
Use when bootstrapping or managing VPS agent environments: fresh install, add project, hex-relay redeploy, diagnostics, or fleet plan/apply.
Use when installing, verifying, or updating the shared VPS host runtime for Claude Code, Codex, MCP, and marketplace plugins.
Use when creating or verifying one project runtime on a prepared VPS, including god-session, provider credentials, and local dispatcher setup.
Use when deploying, redeploying, verifying, migrating, or syncing users for the hex-relay Telegram/API control plane on a VPS.
Use when inspecting health, drift, logs, auth, ports, systemd, tmux, or safe repair needs for one VPS project environment.
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
| name | ln-314-review-repair-worker |
| description | Use when accepted findings require bounded repair changes and a structured repair summary. |
| license | MIT |
Paths: File paths (
shared/,references/,../ln-*) are relative to skills repo root.
Type: L3 Worker Category: 3XX Planning
MANDATORY READ: Load shared/references/evaluation_worker_runtime_contract.md, shared/references/evaluation_summary_contract.md, shared/references/cleanup_evidence_contract.md
MANDATORY READ: Load ../ln-310-multi-agent-validator/references/plan_review_pipeline.md, ../ln-310-multi-agent-validator/references/penalty_points.md
MANDATORY READ: Load ../ln-310-multi-agent-validator/references/structural_validation.md, ../ln-310-multi-agent-validator/references/standards_validation.md, ../ln-310-multi-agent-validator/references/solution_validation.md, ../ln-310-multi-agent-validator/references/workflow_validation.md, ../ln-310-multi-agent-validator/references/quality_validation.md, ../ln-310-multi-agent-validator/references/dependency_validation.md, ../ln-310-multi-agent-validator/references/cross_reference_validation.md, ../ln-310-multi-agent-validator/references/risk_validation.md, ../ln-310-multi-agent-validator/references/premortem_validation.md, ../ln-310-multi-agent-validator/references/traceability_validation.md
mode=story: full 11-group repair using findings from ln-312mode=plan_review: apply accepted corrections only (max 5 corrections per ../ln-310-multi-agent-validator/references/plan_review_pipeline.md Compare & Correct Safety Rules)The checklists below are mandatory inputs loaded above. Use the table only as the routing map for applying them.
| # | Group | Criteria | Checklist |
|---|---|---|---|
| 1 | Structural | #1-#4, #23-#24 | ../ln-310-multi-agent-validator/references/structural_validation.md |
| 2 | Standards | #5 | ../ln-310-multi-agent-validator/references/standards_validation.md |
| 3 | Solution | #6, #21, #28 | ../ln-310-multi-agent-validator/references/solution_validation.md |
| 4 | Workflow | #7-#13 | ../ln-310-multi-agent-validator/references/workflow_validation.md |
| 5 | Quality | #14-#15 | ../ln-310-multi-agent-validator/references/quality_validation.md |
| 6 | Dependencies | #18-#19/#19b | ../ln-310-multi-agent-validator/references/dependency_validation.md |
| 7 | Cross-Reference | #25-#26 | ../ln-310-multi-agent-validator/references/cross_reference_validation.md |
| 8 | Risk | #20 | ../ln-310-multi-agent-validator/references/risk_validation.md |
| 9 | Pre-mortem | #27 | ../ln-310-multi-agent-validator/references/premortem_validation.md |
| 10 | Verification | #22 | ../ln-310-multi-agent-validator/references/traceability_validation.md |
| 11 | Traceability | #16-#17, #17b-#17c | ../ln-310-multi-agent-validator/references/traceability_validation.md |
FLAGGED only when human judgment is required and auto-fix cannot safely continue.../ln-310-multi-agent-validator/references/penalty_points.md (do not hardcode).Runtime family:
evaluation-worker-runtimeRequired manifest fields:
identifierphase_ordersummary_kind=review-repairoperation=repairRecommended phase_order:
PHASE_0_CONFIGPHASE_1_LOAD_FINDINGSPHASE_2_GROUP_STRUCTURAL (#1-#4, #23-#24)PHASE_3_GROUP_STANDARDS_SOLUTION (#5, #6, #21, #28)PHASE_4_GROUP_WORKFLOW_QUALITY (#7-#15)PHASE_5_GROUP_DEPS_XREF (#18-#19/#19b, #25-#26)PHASE_6_GROUP_RISK_PREMORTEM (#20, #27)PHASE_7_GROUP_VERIFICATION_TRACE (#22, #16-#17, #17b-#17c)PHASE_8_VERIFY_LOCAL_RESULTPHASE_9_WRITE_SUMMARYPHASE_10_SELF_CHECKEmit summary_kind=review-repair.
Payload must include:
worker=ln-314statusoperation=repairwarningsPrefer these fields when available:
penalty_before (from ln-312 findings)penalty_after (after repairs)flagged_items (list of items requiring human judgment)coverage_summary (AC coverage percentage)groups_processed (count)review-repair summary writtenVersion: 1.0.0 Last Updated: 2026-04-10