| Deterministically merge the final fingerprinted section snapshot into `output/DRAFT.md`, preserving outline order and inserting transitions only when explicitly enabled.
npx skills add https://github.com/WILLOSCAR/research-units-pipeline-skills --skill section-merger
Goal: assemble a paper-like output/DRAFT.md from:
sections/ (per-section/per-subsection prose)outline/transitions.md (optional hand-off suggestions; generated by transition-weaver)outline/tables_appendix.md (reader-facing Appendix tables; generated by appendix-table-writer)Merge order is driven by outline/outline.yml. The draft title is derived from
GOAL.md when present. When sections/sections_manifest.jsonl is supplied by
the Pipeline contract, every merged section must match its recorded bytes and
SHA-256 hash.
This skill is deterministic: it does not rewrite content or invent prose; it only merges already-generated artifacts.
outline/transitions.insert_h3.ok.outline/transitions.insert_h2.ok.- 3.1 -> 3.2: <text>.→ is accepted, but -> is the preferred contract (avoids control-character encoding issues).post-merge-voice-gate after merging, and route fixes back to outline/transitions.md (do not patch the merged draft).This pipeline uses two table layers:
outline/tables_index.md (internal index; produced by table-filler)outline/tables_appendix.md (reader-facing Appendix tables; produced by appendix-table-writer)section-merger under a single Appendix headingsection-merger inserts outline/tables_appendix.md at the end of the draft under ## Appendix: Tables.# headings inside the tables file are stripped).outline/tables.insert.off in the workspace.outline/outline.yml (drives section/subsection order)outline/transitions.md (required)sections/sections_manifest.jsonl (required by the executable survey Pipeline; freshness gate)GOAL.md (optional title)For arxiv-survey pipelines (default contract):
outline/tables_appendix.md (required unless opted out)output/DRAFT.mdoutput/MERGE_REPORT.mduv run python .codex/skills/section-merger/scripts/run.py --helpuv run python .codex/skills/section-merger/scripts/run.py --workspace <workspace>--workspace <workspace> (required)--unit-id <id> (optional; used only for runner bookkeeping)--inputs <a;b;c> (optional; override inputs; defaults are profile-aware)--outputs <draft_rel;report_rel> (optional; defaults to output/DRAFT.md;output/MERGE_REPORT.md)--checkpoint <C#> (optional; ignored by the merger)uv run python .codex/skills/section-merger/scripts/run.py --workspace <workspace>
uv run python .codex/skills/section-merger/scripts/run.py --workspace <workspace> --outputs output/DRAFT.md;output/MERGE_REPORT.md
Likely cause:
sections/*.md file has not been written yet.Fix:
sections/ (typically via subsection-writer) and rerun merge.Fix:
outline/tables_appendix.md exists and contains the profile minimum(course paper: >=1; survey/deep: >=2) with no placeholders.
outline/tables.insert.off.section-merger.Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.
Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.
Take willoscar/section-merger from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.