plugins/agile-workflow/skills/ln-314-review-repair-worker/SKILL.md
Use when accepted findings require bounded repair changes and a structured repair summary.
npx skillsauth add levnikolaevich/claude-code-skills ln-314-review-repair-workerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
Type: L3 Worker Category: 3XX Planning
MANDATORY READ: Load references/evaluation_worker_runtime_contract.md, references/evaluation_summary_contract.md
MANDATORY READ: Load ../ln-310-multi-agent-validator/references/plan_review_pipeline.md, ../ln-310-multi-agent-validator/references/penalty_points.md
Conditional read: in mode=story, load only the validation checklist files for groups present in accepted findings before applying those group repairs. Load references/cleanup_evidence_contract.md only if background tools or processes are launched.
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 table below is a routing map. Load a checklist only when accepted findings include that group; do not preload unrelated validation catalogs.
| # | 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
testing
Checks runtime lifecycle and config validation: bootstrap, shutdown, probes, cleanup, env sync, and fail-fast startup. Use for runtime readiness.
testing
Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.
testing
Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.
development
Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.