0be354a920
Single-commit clean baseline after security scrub of niche-tells, project codenames, internal jargon, and contributor-email leaks. Contents: - 100 Rust crates (_primitives/_rust/) - 37 agent manifests (_manifests/) + generated specs (_generated/) - 67 user-invocable skills (skills/) - 33 hooks (hooks/) - Composition blocks (_blocks/) - Documentation (docs/, README.md) - TS adapter packages (_ts_packages/) - Assembler (_assembler/) - Roles (_roles/) - Templates (_templates/) - Forgejo CI (.forgejo/) Author: Denis Parfionovich <info@greendragon.info> License: see LICENSE.
1.5 KiB
1.5 KiB
| name | description | arguments | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| refactor | Use when refactoring code while preserving behavior — checkpoint, extract, test, audit |
|
Refactor Workflow
Step 1: Understand Current State
- Read target file(s) completely
- Identify existing tests for the target
- Run existing tests — baseline must pass
- Document current behavior (inputs → outputs)
Step 2: Plan Refactoring
- Identify what violates Constructor Pattern:
- File >200 lines → decompose
- Function >30 lines → extract
- Multiple responsibilities → split
- Duplicated code → single source
- Overlay/patches → root formula
- List concrete changes BEFORE making them
Step 3: Checkpoint
checkpoint: before refactor $target
Step 4: Refactor (Incremental)
- ONE structural change at a time
- After each change: run tests
- If test breaks → fix immediately or revert
- Preserve all public interfaces unless explicitly changing them
Step 5: Audit
- Check: does refactored code follow Constructor Pattern?
- Check: no overlay, no dead code, no orphaned imports
- Check: SSOT — no duplicated logic
- Check: file sizes within limits
Step 6: Final Verification
- Run full test suite — all pass
- Diff review: no accidental behavior changes
- No new dependencies added without reason
Step 7: Commit
refactor: <what was restructured and why>