refactor

Compare live vault configuration against derivation records and plan artifact updates.

6|2|Updated Nov 2, 2022

Search Tags:#automation #refactor #configuration management #vault #system evolution #restructuring

Ready to run

npx skills add https://github.com/arolariu/arolariu.ro --skill refactor-arolariu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/arolariu/arolariu.ro/tree/main/.claude/skills/refactor
Command: npx skills add https://github.com/arolariu/arolariu.ro --skill refactor-arolariu

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill manages the complex cascading effects of configuration changes within a vault system, ensuring all related artifacts are updated consistently and safely.

Core Features & Use Cases

Detect Configuration Drift: Compares current live configuration (config.yaml) against the original design (derivation.md) to identify dimension shifts.
Plan Restructuring: Generates a detailed plan showing affected artifacts (skills, templates, context files, hooks) and potential content impact.
Execute & Audit: Implements approved changes and runs validation checks to ensure system integrity.
Use Case: After deciding to change the vault's organization from "flat" to "hierarchical," this Skill will identify all affected insight templates, update the domain map structure, adjust navigation references in the context file, and regenerate relevant skills, presenting a clear plan for approval before execution.

Quick Start

Use the refactor skill to plan and execute vault restructuring based on changes in ops/config.yaml.

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 when configuration changes affect multiple files?▼

Vault restructuring is automated by comparing live configuration against derivation records to identify dimension shifts, then planning and executing cascading updates across affected skills, templates, context files, and hooks.

What is configuration drift detection in a vault system?▼

Configuration drift detection compares current live configuration files against original design records to identify dimension shifts, highlighting discrepancies that require artifact updates to maintain system integrity.

How do I plan restructuring updates for insights and domain maps after a vault organization change?▼

Restructuring updates are planned by generating a detailed impact analysis showing affected artifacts, such as insight templates and domain map structures, presenting a clear plan for approval before execution.

Can I validate system integrity after executing vault configuration changes?▼

System integrity is validated post-execution through an audit phase that runs validation checks, ensuring all cascading updates across skills, templates, context files, and hooks are applied consistently and safely.

What is the best way to manage cascading configuration changes across context files and hooks?▼

Managing cascading configuration changes is best handled by orchestrating a structured workflow that detects drift, plans artifact updates, and executes modifications with audit validation to ensure consistency.

Do I need a derivation record to restructure my vault configuration?▼

A derivation record is required to detect configuration drift, serving as the original design blueprint that the live configuration is compared against to identify necessary dimension shifts and restructuring actions.