doc-refactoring

Extract mixed content into dedicated Markdown documents and update cross-references.

Updated Aug 27, 2026

Search Tags:#documentation #markdown #refactoring #technical writing #content extraction #separation of concerns

Ready to run

npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill doc-refactoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: doc-refactoring
Source: https://github.com/reeinharddd/impulsa-monorepo/tree/main/.github/skills/doc-refactoring
Command: npx skills add https://github.com/reeinharddd/impulsa-monorepo --skill doc-refactoring

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the issue of mixed concerns within documentation, where different types of information (like database schemas, API endpoints, or UI flows) are incorrectly placed in the wrong documents, leading to confusion and duplication.

Core Features & Use Cases

Separation of Concerns Enforcement: Ensures each document type contains only its primary content, referencing other types as needed.
Content Extraction and Relocation: Moves misplaced content to its correct, dedicated document.
Use Case: If a database schema document mistakenly includes UI interaction details, this Skill will extract those UI details into a separate UX document and update the database document to simply reference the new UX document.

Quick Start

Use the doc-refactoring skill to fix documentation violations by extracting mixed concerns into separate documents.

Frequently Asked Questions about doc-refactoring

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

FAQPage Schema

How do I fix mixed concerns in markdown documentation files?▼

To fix mixed concerns in markdown documentation, you must enforce separation of concerns by extracting misplaced content into dedicated documents and updating cross-references to maintain content integrity.

What is the best way to extract misplaced UI details from a database schema document?▼

The best way to extract misplaced UI details from a database schema document is to relocate the content into a separate UX document and update the original file to reference the new location.

How does documentation refactoring handle cross-references when content is moved?▼

Documentation refactoring handles cross-references by moving misplaced content to a dedicated document and updating the original file to reference the new location, ensuring content integrity and maintainability.

Can I apply separation of concerns to all markdown files in the docs directory?▼

Yes, you can apply separation of concerns to all markdown files within the docs directory, ensuring each document type contains only its primary content and references other types as needed.

When do I need to refactor technical writing to enforce a matrix of document types?▼

You need to refactor technical writing to enforce a matrix of document types when different information types like API endpoints and UI flows are incorrectly placed in the wrong documents, causing confusion and duplication.

Does documentation refactoring require predefined rules for content extraction?▼

Yes, documentation refactoring requires adherence to a defined matrix of document types and their primary content responsibilities to correctly extract mixed content into dedicated documents.