refactor

Detect configuration drift between ops/config.yaml and ops/derivation.md.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/achousal/EngramR --skill refactor-achousal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/achousal/EngramR/tree/main/.claude/skills/refactor
Command: npx skills add https://github.com/achousal/EngramR --skill refactor-achousal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and manage configuration drift between live configuration and baseline derivation to surface safe, approvable restructuring plans. It codifies an end-to-end workflow that identifies changes, assesses impact across artifacts, and orchestrates updates to skills, context, templates, and documentation while preserving provenance.

Core Features & Use Cases

  • Drift detection: compares ops/config.yaml against ops/derivation.md to reveal mismatches.
  • Impact analysis: maps each Changed dimension to affected artifacts and content migrations.
  • Safe execution: generates a delta plan, requests explicit approval, and then applies changes in controlled phases.
  • Documentation and provenance: updates derivation records, changelog, and kernel validation status to maintain traceability.
  • Skill regeneration: regenerates affected skills and updates context accordingly.

Quick Start

Run the refactor workflow to detect drift and produce an approved restructuring plan.

Frequently Asked Questions about refactor

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

FAQPage Schema
How do I detect configuration drift between my baseline derivation and live config files?

Configuration drift is detected by comparing ops/config.yaml against ops/derivation.md to reveal mismatches. This comparison surfaces actionable restructuring opportunities by mapping each changed dimension to affected artifacts and required content migrations.

What is the safest way to plan a vault restructuring after changing config.yaml?

The safest vault restructuring approach generates a delta plan detailing affected artifacts, risks, and content implications. It requires explicit approval before executing any changes, ensuring updates to skills, context, and documentation are applied in controlled phases.

How do I manage documentation updates and provenance when refactoring config files?

Documentation updates and provenance are managed by recording derivation records, changelogs, and kernel validation status. This maintains traceability throughout the workflow, coordinating skill regeneration and context updates alongside the applied configuration changes.

Can I execute config changes automatically without approval during a refactor?

No, config changes cannot execute without approval. The workflow generates a delta plan and requests explicit confirmation before applying any changes, ensuring safe execution and validating through kernel checks to preserve system integrity.

What happens to affected skills when config.yaml and derivation.md drift apart?

Affected skills are regenerated and their context is updated automatically when drift is resolved. The workflow coordinates these changes alongside documentation updates and kernel validation to maintain traceability across the restructured artifacts.