skills.rest
bkinsey808
bkinsey808COMMUNITY
Explore all skills by this author →
𝕏@bkinsey808GitHub

file-splitting

Split monolithic files into single-function modules with default exports and colocated tests.

Updated Aug 23, 2026
Search Tags:#typescript#refactoring#modularization#test-organization#single-responsibility#absolute-imports#default-exports
One-click install
npx skills add https://github.com/bkinsey808/songshare-effect --skill file-splitting
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: file-splitting
Source: https://github.com/bkinsey808/songshare-effect/tree/main/.github/skills/file-splitting
Command: npx skills add https://github.com/bkinsey808/songshare-effect --skill file-splitting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Large codebases often accumulate monolithic files that house many exports and test helpers, making maintenance, testing, and reuse painful.

Core Features & Use Cases

  • Single responsibility – one function per file
  • Naming conventions – camelCase for functions, PascalCase for components
  • Export patterns – default exports for single symbols
  • Import paths – Absolute paths for portability
  • Test colocations – Tests colocated with their source files
  • Validation – Linting, typing, and test verification

Quick Start

Split a large consolidated file into individual files with one export per file and colocated tests.

Frequently Asked Questions about file-splitting

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

FAQPage Schema
How do I split large TypeScript files into single responsibility modules?▼

Split large TypeScript files by breaking monolithic code into individual modules with one default export per file. This enforces single responsibility, uses absolute imports for portability, and colocates tests with source files.

What is the best way to refactor monolithic test helpers into focused modules?▼

Refactor test helpers by splitting consolidated files into individual, testable modules. This process applies a strict, path-stable workflow to ensure safe migration while maintaining test colocations alongside their source files.

Can I use absolute imports and default exports when modularizing code?▼

Yes, absolute imports and default exports are enforced during modularization. Absolute paths ensure import portability across directory depths, while default exports restrict each file to a single exported symbol.

Does this modularization approach maintain import paths during file migration?▼

Yes, a strict, path-stable workflow ensures safe migration. Absolute import paths prevent breakage across directory depths, and explicit optional directories for scripts, references, and assets maintain structure during the split.

How do I validate refactored modules after splitting a large file?▼

Validate refactored modules by running linting, typing, and test verification checks. This ensures the split files maintain their expected behavior and that colocated tests pass after the modularization process.

Related Skills

Explore More Software Engineering Skills→
GaryOcean428GaryOcean428

import-resolution

Identify and fix Python import errors and validate __init__.py exports.

Community
Intermediate
paleoterrapaleoterra
2

sqlite-test-validator

Validate SQLite migrations and schemas with sqlite_validator.py CLI commands.

Community
Intermediate
Marshall-HallenbeckMarshall-Hallenbeck
5

write-tests

Generate unit tests for Python, JavaScript, TypeScript, Rust, and Go modules.

Community
Advanced
earthy-zincearthy-zinc

doc-organizer

Identify and reorganize documentation structures by removing duplicates and enforcing naming standards.

Community
Advanced