How do I install the Organize skill?

Run npx skillmds@latest add recrsn/organize in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Organize skill do?

Split large files into manageable chunks following language-specific best practices It is listed under Coding & Dev Tools on SkillMD.

Is Organize safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Organize?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Organize free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Organize?

recrsn (@recrsn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Organize by recrsn — Agent Skill

Name: Organize
Author: recrsn

File contents

Check the diff against origin/main, and identify large files that were added or modified in this branch. Run git fetch origin to make sure git context is up-to-date.

Here is the list of files changed in this branch: !git diff --name-only origin/main

For each changed file, read the full file and determine if it should be split based on the language conventions below. Then execute the splits, updating all imports and references across the project.

When to split

Files over ~300 lines are candidates; over ~500 should almost always be split
Files with multiple unrelated concepts or public exports
Keep tightly coupled code together — don't split just to hit a line count
Helper/utility functions used by only one caller stay with the caller
One major class/component per file (applies across all languages)
Group small related types (enums, data classes) together

Language-specific additions

TypeScript / JavaScript / React

Colocate component styles and tests alongside the component
Redux: ducks pattern — one slice file per domain
Shared types/interfaces go in types.ts; barrel exports (index.ts) for directory API

Swift / SwiftUI

Previews stay with their view; protocols and default extensions can share a file

Java / Kotlin

Inner classes stay with outer class unless large and used externally
Kotlin: data classes used by only one file can stay

Python

Separate CLI entry points from library code

Go

Group by responsibility: types, handlers, middleware
Keep interfaces near dependents, not implementations
Test files mirror source files (foo.go → foo_test.go)

Rules

Only split files touched by the branch diff
Preserve external behavior exactly; all existing imports must continue to work
Follow the project's existing naming and directory conventions over the guidelines above
Do not rename exported symbols — only move them
Update all imports, references, and re-exports; verify no circular dependencies
Run the project's linter/formatter if configured
When in doubt, leave the code together

Report at the end with a brief summary of files split and the rationale.

---name: organizedescription: Split large files into manageable chunks following language-specific best practices---Check the diff against origin/main, and identify large files that were added ormodified in this branch. Run `git fetch origin` to make sure git context isup-to-date.Here is the list of files changed in this branch:!`git diff --name-only origin/main`For each changed file, read the full file and determine if it should be splitbased on the language conventions below. Then execute the splits, updating allimports and references across the project.## When to split- Files over ~300 lines are candidates; over ~500 should almost always be split- Files with multiple unrelated concepts or public exports- Keep tightly coupled code together — don't split just to hit a line count- Helper/utility functions used by only one caller stay with the caller- One major class/component per file (applies across all languages)- Group small related types (enums, data classes) together## Language-specific additions### TypeScript / JavaScript / React- Colocate component styles and tests alongside the component- Redux: ducks pattern — one slice file per domain- Shared types/interfaces go in `types.ts`; barrel exports (`index.ts`) for directory API### Swift / SwiftUI- Previews stay with their view; protocols and default extensions can share a file### Java / Kotlin- Inner classes stay with outer class unless large and used externally- Kotlin: data classes used by only one file can stay### Python- Separate CLI entry points from library code### Go- Group by responsibility: types, handlers, middleware- Keep interfaces near dependents, not implementations- Test files mirror source files (`foo.go` → `foo_test.go`)## Rules- Only split files touched by the branch diff- Preserve external behavior exactly; all existing imports must continue to work- Follow the project's existing naming and directory conventions over the guidelines above- Do not rename exported symbols — only move them- Update all imports, references, and re-exports; verify no circular dependencies- Run the project's linter/formatter if configured- When in doubt, leave the code togetherReport at the end with a brief summary of files split and the rationale.

Frequently asked questions

Organize