skills.rest
kamilseghrouchni
kamilseghrouchniCOMMUNITY
Explore all skills by this author →
GitHub

compile-resolve

Analyze fragment files and wiki index to generate a resolution_plan.json.

Updated Mar 31, 2026
Search Tags:#planning#merge#wiki#resolve#entity#dry-run#fragment
One-click install
npx skills add https://github.com/kamilseghrouchni/vcro-sourcing --skill compile-resolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compile-resolve
Source: https://github.com/kamilseghrouchni/vcro-sourcing/tree/main/.claude/skills/compile/resolve
Command: npx skills add https://github.com/kamilseghrouchni/vcro-sourcing --skill compile-resolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dry-run entity resolution for the vCRO v2 compiler to determine how hints should be integrated without altering the wiki.

Core Features & Use Cases

  • Deterministic analysis of fragment files and the wiki index to classify hints as NEW, MERGE_INTO, or AMBIGUOUS for the merge phase.
  • Eyeballable output that produces a resolution_plan.json describing planned actions, enabling safe validation before wiki changes.

Quick Start

Run the resolve phase with your fragment files and the wiki index to generate resolution_plan.json at the specified output location.

Frequently Asked Questions about compile-resolve

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

FAQPage Schema
How do I dry-run entity resolution for a wiki index without modifying files?▼

Dry-run entity resolution analyzes fragment files and the wiki index to generate a resolution_plan.json classifying hints as NEW, MERGE_INTO, or AMBIGUOUS without altering the wiki. This enables safe validation before committing any merge changes.

What is entity resolution classification for fragment hints during a merge?▼

Entity resolution classification evaluates fragment hints against a master wiki index to categorize each hint as NEW, MERGE_INTO, or AMBIGUOUS. It produces a deterministic resolution_plan.json file to guide the upcoming merge phase safely.

Can I validate fragment file integration before applying changes to the wiki?▼

Yes, you can validate fragment file integration by running a deterministic dry-run that outputs a resolution_plan.json. This plan details all planned actions, allowing you to review and validate safely before any wiki modifications occur.

How do I generate a resolution plan for vCRO v2 using fragment files?▼

Generate a resolution plan by running the resolve phase with your input fragment files and the wiki index. The process reads the master.md index, classifies hints, and writes the resolution_plan.json to your specified output path.

Does the entity resolution process require a specific wiki index format?▼

The entity resolution process requires reading the master wiki index located at store/wiki/index/master.md. It uses this specific index file alongside your input fragment files to deterministically classify hints for the merge phase.

Why are some entity resolution hints classified as AMBIGUOUS in the plan?▼

Hints are classified as AMBIGUOUS when the deterministic analysis of fragment files and the wiki index cannot confidently resolve them as either NEW or MERGE_INTO. This classification flags unclear integrations for manual review before the merge phase.

Related Skills

Explore More Software Engineering Skills→
kamilseghrouchnikamilseghrouchni

compile-merge

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

Community
Advanced
2389-research2389-research
90

landing-page-design

Generate landing-page concepts with brand context and design briefs.

Official
Advanced
wzdavidwzdavid
30

ThinkWiki

Initialize and maintain a local Markdown knowledge base with automated inbox management.

Community
Advanced
netguy204netguy204
3

entity-shutdown

Consolidate session memories into persistent tiers via the ve entity shutdown command.

Community
Advanced