skill-refactorer

Refactor SKILL.md files by applying seven patterns to keep orchestrators under 100 lines.

3|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/ryryo/dot-claude-dev --skill skill-refactorer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-refactorer
Source: https://github.com/ryryo/dot-claude-dev/tree/main/.claude/skills/skill-refactorer
Command: npx skills add https://github.com/ryryo/dot-claude-dev --skill skill-refactorer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps developers restructure overly long SKILL.md files by applying seven refactoring patterns to create a concise orchestrator under 100 lines.

Core Features & Use Cases

  • Apply seven refactoring patterns: compression, DRY, LLM action control, gate conditions, separation of concerns, deprecation/cleanup, and structuring.
  • Move details to agents/ and references/ to keep SKILL.md short and maintainable.
  • Ensure SKILL.md remains under 100 lines for readability and consistency.

Quick Start

  1. Run the skill on the target SKILL.md to begin the refactor.
  2. Review the proposed changes and approve or adjust as needed.
  3. Save the updated SKILL.md and verify that it remains within the 100-line limit.

Frequently Asked Questions about skill-refactorer

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

FAQPage Schema
How do I refactor a SKILL.md file to stay under 100 lines?

To refactor a SKILL.md file under 100 lines, apply seven refactoring patterns like compression and DRY, moving detailed content into dedicated agents/ and references/ directories to create a compact orchestrator.

What patterns help compress a long SKILL.md orchestrator?

Patterns that help compress a SKILL.md orchestrator include compression, DRY, LLM action control, gate conditions, separation of concerns, deprecation cleanup, and structuring to isolate details into modular files.

How do I separate concerns when modularizing SKILL.md documentation?

Separate concerns when modularizing SKILL.md documentation by moving implementation details to references/ and agents/ directories, leaving only orchestration logic in the root file to enforce a strict line limit.

Does refactoring a SKILL.md file delete content from agents/ and references/?

Refactoring a SKILL.md file does not delete content from agents/ and references/; it preserves those details while compressing the root orchestrator file to ensure it remains under 100 lines.

What is the best way to apply DRY principles to SKILL.md files?

The best way to apply DRY principles to SKILL.md files is using a structured Read, Edit, and AskUser workflow to identify repetitive content, move it to references/, and verify the orchestrator stays under 100 lines.