Organize
Repository structure only: directory layout, file placement, naming conventions, and...
Install
npx skills add SethGammon/Citadel --skill organize -g -a claude-code -y- Repository
- SethGammon/Citadel927
- Category
- Engineering
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 1,510 tokens
- Runs scripts
- No, instructions only
What it does
Repository structure only: directory layout, file placement, naming conventions, and where-does-this-belong decisions. Detects the project's convention, audits files against it, and executes move plans with import-path updates. Never changes code inside files beyond the import updates a move forces; in-file restructuring is /refactor.
/organize -- Repository Structure
Orientation
Use when: Deciding where a file belongs, auditing file placement against the project's conventions, running a naming-convention sweep, or moving files so the tree matches the declared layout.
Don't use when: You want a structural map of code relationships (use /map), you want to change code inside files (use /refactor), you need disk or artifact cleanup (use /houseclean), or you need a single known move executed (use /refactor move).
Boundary with /refactor
/organize changes where files live and what they are named. Changing code structure within files (extract, inline, split functions or components, rename symbols) is /refactor. The only in-file edits /organize makes are import-path updates forced by a move or rename. If an audit reveals a file that should be split or merged, recommend /refactor; do not do it here.
Commands
| Command | Behavior |
|---|---|
/organize | Detect convention, audit placement, propose and execute a move plan |
/organize --audit | Check current files against the manifest, report violations only |
/organize --show | Display the current organization manifest |
/organize --lock | Set locked: true so the enforcement hook blocks violations |
/organize --unlock | Set locked: false so enforcement is advisory |
/organize where does {file} go | Single placement decision, no full audit |
Protocol
Step 1: CHECK
Read .claude/harness.json, Citadel's shared config path for all runtimes including Codex. If an organization key exists, use its convention and placement rules; on bare /organize, ask whether to audit, adjust the rules, or reconfigure. If no key exists, continue to Step 2.
