Fork Discipline
jezweb/claude-skillsA multi-client project has two kinds of code: core and client. Core is shared by every deployment. Client is unique to each one. When these get mixed together, the project becomes hard to maintain. This skill finds where the boundary is blurred.
It scans your codebase and creates a boundary map. It lists every violation where client code hides in core. Then it gives you a refactoring plan to separate them cleanly. You can also generate a FORK.md document and restructuring scripts.
Use this when adding a new client, before a big refactor, or just to keep your project healthy. It works with common patterns like client directories, multiple packages, and runtime client settings.
Add Fork Discipline skill to your workflow
Global
mkdir -p ~/.claude/skills/fork-disciplineProject
mkdir -p .claude/skills/fork-disciplineSource Repository
More Code Review & Quality Claude Code Skills
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective