refactor

Compare live config.yaml against derivation.md to plan and execute vault restructuring.

20|5|Updated Nov 18, 2025
One-click install
npx skills add https://github.com/zby/llm-do --skill refactor-zby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/zby/llm-do/tree/main/arscontexta/skills/arscontexta-refactor
Command: npx skills add https://github.com/zby/llm-do --skill refactor-zby

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of restructuring your vault based on configuration changes, ensuring consistency across all artifacts and preventing drift.

Core Features & Use Cases

  • Detect Configuration Drift: Compares your live configuration (config.yaml) against its original derivation (derivation.md) to identify all dimension and feature flag changes.
  • Plan Restructuring: Analyzes the cascading effects of each change on artifacts like skills, templates, MOCs, and context files, providing a detailed plan.
  • Execute on Approval: Implements the planned changes after user confirmation, including content migration and validation.
  • Use Case: You decide to change your vault's organization from "flat" to "hierarchical". This Skill will identify all affected files, MOCs, and templates, show you exactly what needs to be moved or updated, and then perform the restructuring for you after you approve.

Quick Start

Use the refactor skill to plan and execute changes to your vault's configuration.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I automate vault restructuring after changing configuration settings?

Automate vault restructuring by comparing live configuration files against derivation records to identify dimension shifts, analyze cascading impacts on artifacts, and execute changes upon approval. This detects configuration drift and migrates content automatically while validating system integrity.

What is configuration drift and how does it affect data management in a vault?

Configuration drift occurs when live settings diverge from their original derivation records, causing inconsistencies across artifacts like skills, templates, and MOCs. Detecting this drift involves comparing current configurations against baseline derivations to identify all dimension and feature flag changes.

How do I plan hierarchical changes to my vault without breaking existing templates?

Plan hierarchical changes by analyzing the cascading effects of dimension shifts on templates, MOCs, and context files. The system generates a detailed restructuring plan showing exactly what needs updating, then executes content migration only after you review and approve the proposed changes.

Can I validate vault integrity automatically after migrating content?

Yes, you can validate vault integrity automatically after migrating content. Post-restructuring validation runs immediately after execution to ensure system integrity, verifying that all artifacts, skills, and templates align correctly with the updated configuration without manual checks.

What's the best way to migrate from a flat to a hierarchical vault organization?

The best way to migrate from flat to hierarchical organization is using configuration drift detection to identify all affected files, MOCs, and templates. The system calculates cascading impacts, presents a detailed migration plan, and restructures the vault automatically upon your approval.

When should I avoid automated workflow restructuring for my vault configuration?

You should avoid automated workflow restructuring if your vault lacks a derivation record to compare against live configurations. Without this baseline, the system cannot detect dimension shifts or calculate cascading impacts on artifacts, making automated content migration unsafe.