refactor

Name: refactor
Availability: InStock
Author: agenticnotetaking

Detect configuration drift between config.yaml and derivation.md, then plan vault restructuring.

3.5k|220|Updated Feb 15, 2026

Search Tags:#knowledge management #drift detection #configuration #refactor #system maintenance #restructuring

Ready to run

npx skills add https://github.com/agenticnotetaking/arscontexta --skill refactor-agenticnotetaking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: refactor
Source: https://github.com/agenticnotetaking/arscontexta/tree/main/skill-sources/refactor
Command: npx skills add https://github.com/agenticnotetaking/arscontexta --skill refactor-agenticnotetaking

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining consistency between your knowledge system's configuration and its actual implementation, preventing drift and ensuring your system evolves predictably.

Core Features & Use Cases

Configuration Drift Detection: Compares your current config.yaml against the original derivation.md to identify discrepancies in system dimensions.
Restructuring Planning: Generates a detailed plan for how to update affected artifacts (skills, templates, context files) based on detected configuration changes.
Controlled Execution: Requires explicit user approval before applying any changes, ensuring safety and predictability.
Use Case: After running /architect suggests changing your vault's organization from "flat" to "hierarchical", you use /refactor to see exactly which files will be moved, which MOCs need updating, and to get a plan for executing these changes safely.

Quick Start

Run /refactor to see if your vault's configuration has drifted from its original design.

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 in my knowledge vault?▼

To detect configuration drift, compare your current config.yaml against the original derivation.md. This identifies discrepancies in system dimensions and generates a restructuring plan for affected artifacts.

How do I restructure my knowledge vault after changing system dimensions?▼

You restructure your knowledge vault by generating a detailed plan that identifies affected artifacts like skills, templates, and context files. The system requires explicit user approval before applying any structural changes to ensure safe execution.

What is the safest way to update knowledge management artifacts after an architecture change?▼

The safest way to update knowledge management artifacts is through controlled execution that requires explicit approval before applying changes. Post-restructuring validation ensures system integrity is maintained throughout the reorganization process.

Can I see which files will be moved before executing a vault restructuring?▼

Yes, you can see which files will be moved before execution. The restructuring planning phase generates a detailed overview of affected artifacts and provides a risk assessment for your review prior to any changes being applied.

Do I need an original derivation.md file to detect system configuration drift?▼

Yes, you need an original derivation.md file to detect system configuration drift. It serves as the baseline configuration document that the current config.yaml is compared against to identify any dimensional shifts.

Why does my vault restructuring plan require explicit user approval?▼

Your vault restructuring plan requires explicit user approval to ensure safety and predictability. This controlled execution prevents unintended modifications to skills, templates, and context files before post-restructuring validation verifies system integrity.