large-file-refactor

Topics in the source

• Large File Refactor
• Arguments
• Workflow
• Refactor Plan Format
• Guard Rails
• Completion

This skill is coordination-exempt: skip the ai-coord gate for its declared work. If a slash or dollar invocation already added these instructions to the conversation, follow them directly. In that case, do not invoke this skill again through a skill tool. Use LOC thresholds to discover candidates, then decide whether a split is justified by cohesion, coupling, ownership, and change risk. Source files match above 1000 LOC. Test files use a relaxed 2000 LOC discovery threshold. path: Optional file or directory to scan. Default: current working directory. --include-generated: Include generated, vendored, dependency, and build-output paths that are skipped by default. 1. Resolve the skill directory, then run the helper from the target repository: 2. Preserve the helper's Markdown table as the exhaustive report. Do not omit matching rows, even when the refactor plan only covers a subset. 3. If the helper reports no threshold matches, stop after the report. A match is a candidate, not proof that the file should be split. 4. Draft a refactor plan for the 3 largest files only, unless the user explicitly requested another count. 5. For each candidate, rank split value by mixed responsibilit

This is an excerpt. Refer to the complete source and its current requirements.