blueprint-merge

Blueprint Merge — Collapse Nested Blueprint Back to Flat

The reverse of /blueprint-split. If a previously-split blueprint turns out to be small enough that the nested layout is more friction than benefit, this skill collapses it back into one flat file.

When to Use

• User types /blueprint-merge {dir}
• User says "merge this blueprint back", "분할 취소", "되돌려"
• A previously-split directory has shrunk and the nesting is now noise

Usage

/blueprint-merge src
/blueprint-merge .claude

The argument is the original directory name (use .claude, not _claude).

Instructions

Step 1: Validate Inputs

1. Check the user supplied a directory argument. If not, list nested blueprint directories (ls -d .omniscitus/blueprints/*/ 2>/dev/null) and ask which to merge.

2. Verify the nested directory exists:

   • blueprints/{normalize(dir)}/ (normalize = leading . → _)
   • If not, report that the blueprint isn't currently split and stop.

3. Verify the flat file does not already exist:

   • blueprints/{normalize(dir)}.yaml
   • If both nested directory and flat file exist, the state is ambiguous. Report and ask the user which to keep before proceeding.

Step 2: Read All Nested Files

Read every *.yaml under blueprints/{normalize(dir)}/ except _index.yaml. Parse each one and merge their files: entries into a single map. There should be no key collisions across nested files because each file is keyed by a different bucket — but if there are (e.g., from a manual edit), the later file wins and emit a warning.

Step 3: Write the Flat File

Write the merged result to blueprints/{normalize(dir)}.yaml using the same yaml format the hook produces. Preserve all fields per entry. Sort entries alphabetically by path key for stable diffs.

Step 4: Update migrate-config.yaml

Read .omniscitus/migrate-config.yaml. Remove the entry for the target directory from the blueprint_splits: section. If blueprint_splits becomes empty after the removal, drop the key entirely.