compile-merge

Merge resolution plan fragments into wiki entity articles with atomic writes.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/kamilseghrouchni/vcro-sourcing --skill compile-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: compile-merge
Source: https://github.com/kamilseghrouchni/vcro-sourcing/tree/main/.claude/skills/compile/merge
Command: npx skills add https://github.com/kamilseghrouchni/vcro-sourcing --skill compile-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the integration of resolution plan fragments into the wiki by reading a resolution_plan.json and fragment files and writing entity articles under store/wiki. It ensures idempotent updates, uses atomic temp-then-rename writes, and is gate-kept by a pre-write hook.

Core Features & Use Cases

  • Deterministic plan-driven merges for NEW and MERGE_INTO resolutions.
  • Atomic, idempotent writes to store/wiki to prevent partial updates.
  • Generates a run summary at store/queries/_dev_merge describing created, touched, no-op, and deferred items.

Quick Start

Provide the resolution_plan.json and fragment files to this merge skill to update the wiki.

Frequently Asked Questions about compile-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate idempotent wiki merges from a JSON resolution plan?

Idempotent wiki merges are automated by reading a resolution_plan.json and fragment files to deterministically create or update entity articles under store/wiki, ensuring repeated runs produce the same result without duplication.

What is the best way to prevent partial updates when writing wiki articles?

Preventing partial wiki updates requires atomic writes using a temp-then-rename mechanism, ensuring entity articles are only committed when fully generated, avoiding corruption from incomplete save operations.

How do I merge fragments into existing entity articles deterministically?

Merging fragments into existing entity articles is handled through MERGE_INTO resolutions defined deterministically in a resolution_plan.json, updating content while respecting domain-specific frontmatter and provenance schemas.

What does a wiki-merge run summary include for created and deferred items?

A wiki-merge run summary includes categorized item counts for created, touched, no-op, and deferred entries, outputted to store/queries/_dev_merge to track the integration of NEW and MERGE_INTO resolutions.

Can I gate wiki file writes with a pre-write hook before committing articles?

Gating wiki file writes with a pre-write hook is supported, allowing custom validation logic to execute before atomic temp-then-rename operations commit entity articles to the store/wiki directory.

Why does my wiki merge skip certain fragments during plan execution?

Wiki merges skip fragments when resolutions are marked as no-op or deferred, as the deterministic plan strictly processes only NEW and MERGE_INTO operations matching the provided provenance schema.