ln-314-review-repair-worker
Use when accepted findings require bounded repair changes and a structured repair summary.
What this skill does
> **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 in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.