Review Repair Worker
Use when accepted findings require bounded repair changes and a structured repair summary.
MCP get_skill({ skillId: "review-repair-worker-23fd05e3" })Use this skill with your agent
Create a free account and connect via MCP
> **Paths:** File paths (`references/`, `../ln-*`) are relative to this skill directory. **Type:** L3 Worker **Category:** 3XX Planning # Review Repair Worker ## Mandatory Read **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. ## Purpose - apply accepted low-risk repairs using the 11-group systematic validation structure - keep repairs separate from aggregation and approval - record cleanup evidence if background tools are launched ## Mode Gate - `mode=story`: full 11-group repair using findings from ln-312 - `mode=plan_review`: apply accepted corrections only (max 5 corrections per `../ln-310-multi-agent-validator/references/plan_review_pipeline.md` Compare & Correct Safety Rules) ## 11-Group Validation Structure (mode=story) 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` | ## Repair Rules - Zero out penalty points only when the defect is actually repaired (not just acknowledged). - Use `FLAGGED` only when human judgment is required and auto-fix cannot safely continue. - Maximum penalty per `../ln-310-multi-agent-validator/references/penalty_points.md` (do not hardcode). - Test strategy section may exist but remain empty. - Apply auto-fix actions exactly as specified in each checklist's "Auto-fix actions" column. ## Runtime Runtime family: - `evaluation-worker-runtime` Required manifest fields: - `identifier` - `phase_order` - `summary_kind=review-repair` - `operation=repair` Recommended `phase_order`: 1. `PHASE_0_CONFIG` 2. `PHASE_1_LOAD_FINDINGS` 3. `PHASE_2_GROUP_STRUCTURAL` (#1-#4, #23-#24) 4. `PHASE_3_GROUP_STANDARDS_SOLUTION` (#5, #6, #21, #28) 5. `PHASE_4_GROUP_WORKFLOW_QUALITY` (#7-#15) 6. `PHASE_5_GROUP_DEPS_XREF` (#18-#19/#19b, #25-#26) 7. `PHASE_6_GROUP_RISK_PREMORTEM` (#20, #27) 8. `PHASE_7_GROUP_VERIFICATION_TRACE` (#22, #16-#17, #17b-#17c) 9. `PHASE_8_VERIFY_LOCAL_RESULT` 10. `PHASE_9_WRITE_SUMMARY` 11. `PHASE_10_SELF_CHECK` ## Summary Emit `summary_kind=review-repair`. Payload must include: - `worker=ln-314` - `status` - `operation=repair` - `warnings` Prefer 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) ## Definition of Done - [ ] Findings loaded from ln-312 - [ ] All 11 groups processed (mode=story) or accepted corrections applied (mode=plan_review) - [ ] Penalty before/after tracked - [ ] FLAGGED items recorded - [ ] Local verification completed - [ ] Cleanup evidence recorded when needed - [ ] `review-repair` summary written - [ ] Self-check passed **Version:** 1.0.0 **Last Updated:** 2026-04-10
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Pipeline Orchestrator
Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.
Story Coordinator
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
Story Replanner
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.