asset-reconciliation

Detect, classify, and reconcile generated and manual project assets during setup re-runs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/Kiwi-Home/ai-workflow --skill asset-reconciliation
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: asset-reconciliation
Source: https://github.com/Kiwi-Home/ai-workflow/tree/main/plugins/structured-workflows/skills/asset-reconciliation
Command: npx skills add https://github.com/Kiwi-Home/ai-workflow --skill asset-reconciliation

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

Re-running setup can inadvertently overwrite or inconsistently handle previously generated assets, causing nondeterministic builds, lost manual edits, and confusion about provenance; this Skill provides a deterministic protocol to detect, classify, and safely reconcile those assets.

Core Features & Use Cases

  • Provenance Classification: Detects generated vs manual assets using YAML frontmatter, meta blocks, and provenance markers across agents, skills, workflow.yaml, and CLAUDE.md variants.
  • Disposition Actions & Preflight: Presents a preflight report with [created], [updated], [skipped], and [migrated] dispositions and lets users approve selective merges or regenerations.
  • Safe Merge & Optimization: Applies selective deep-merge rules for workflow.yaml, supports source-hash generation-time skips, and preserves user-owned keys while updating template-owned keys.
  • Orphan Detection & Reporting: Flags context-file orphans and migration artifacts for user review without auto-deletion.
  • Use Case: Use when re-running structured-workflows:setup on a repo to avoid overwriting user-authored CLAUDE.md content while updating generated skills and agents.

Quick Start

Run asset-reconciliation during a structured-workflows setup re-run to detect, classify, and propose dispositions for existing assets and present a preflight report.

Frequently Asked Questions about asset-reconciliation

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

FAQPage Schema
How do I prevent a setup re-run from overwriting manual edits in CLAUDE.md?โ–ผ

Asset reconciliation prevents setup re-runs from overwriting manual edits by detecting provenance markers and classifying files as generated or manual, preserving user-authored content while selectively updating template-owned sections.

How does selective merge work for workflow.yaml reconciliation?โ–ผ

Selective merge for workflow.yaml reconciliation applies deep-merge rules that preserve user-owned keys while updating template-owned keys, ensuring deterministic configuration updates without losing custom modifications.

What is provenance classification for generated project assets?โ–ผ

Provenance classification for generated assets is the process of detecting whether files like agents, skills, and context files were generated or manually authored by inspecting YAML frontmatter, meta blocks, and provenance markers.

Can I review and approve asset dispositions before a setup pipeline applies changes?โ–ผ

Yes, you can review asset dispositions before changes are applied using the preflight report, which presents created, updated, skipped, and migrated actions for user confirmation prior to executing selective merges or regenerations.

Does asset reconciliation detect orphaned context files during setup re-runs?โ–ผ

Yes, asset reconciliation detects orphaned context files and migration artifacts during setup re-runs, flagging them in a report for user review without auto-deleting any flagged files.

When should I use source-hash regeneration optimizations for project assets?โ–ผ

Use source-hash regeneration optimizations when re-running setup pipelines on existing codebases to skip unnecessary file generation, applying idempotency checks to avoid redundant rebuilds of unchanged generated assets.