Files
Jeremy Dawes 880c4228c4 feat: add fork-discipline skill — audit core/client boundary in multi-client projects
Three modes:
- audit: map the boundary, find violations (hardcoded client checks,
  config replacement, scattered client code, missing extension points,
  migration conflicts), produce a health score and report
- document: generate FORK.md documenting the boundary and how to add clients
- refactor: concrete steps to move client code out of core, replace client
  checks with feature flags, implement config merge, add extension points

Includes the "right time to run" guide: don't refactor at 1 client,
audit at 2, full refactor at 3+.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-19 11:04:43 +11:00

482 B

description, argument-hint
description argument-hint
Audit and enforce the core/client boundary in multi-client codebases [audit|document|refactor]

Load the fork-discipline skill.

Parse $ARGUMENTS for mode:

  • audit — map the boundary, find violations, produce a report (default)
  • document — generate FORK.md for the project
  • refactor — audit then produce concrete refactoring steps and scripts

Examples: /fork-discipline, /fork-discipline audit, /fork-discipline refactor