plugins/agile-workflow/skills/ln-315-review-merge-worker/SKILL.md
Use when an evaluation run must merge research, findings, documentation, and repair outputs into one verified result.
npx skillsauth add levnikolaevich/claude-code-skills ln-315-review-merge-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
This worker does not launch agents. It consumes worker summaries and existing agent result artifacts after the evaluation runtime barrier. Do not mark an agent failed from elapsed time alone; accept only the runtime's resolved status or result metadata as the completion signal.
For every agent suggestion:
Runtime family:
evaluation-worker-runtimeRequired manifest fields:
identifierphase_ordersummary_kind=review-mergeoperation=mergeRecommended phase_order:
PHASE_0_CONFIGPHASE_1_LOAD_WORKER_RESULTSPHASE_2_DEDUPLICATE_AND_VERIFYPHASE_3_WRITE_SUMMARYPHASE_4_SELF_CHECK.hex-skills/agent-review/review_history.md for prior review entries.AGREE or REJECT.Emit summary_kind=review-merge.
Payload must include:
worker=ln-315statusoperation=mergewarningsPrefer these fields when available:
merge_summary.accepted_countmerge_summary.rejected_countmerge_summary.dedup_removedmerge_summary.architecture_gate_rejectionsSave updated review summary to .hex-skills/agent-review/review_history.md.
pass=true only after summary write.review_history.mdreview-merge 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.