Skip to content

gpsaggese/helpers / .claude/skills/coding.reorg_functions

coding.reorg_functions

Verified

Reorganize the Python functions in a file

FileKindSize
SKILL.mdskill md1.6 KB
---
description: Reorganize the Python functions in a file
model: haiku
---

# Reorganize Python Functions Within a File

- Reorganize the Python functions in the user-provided file per the general
  rules in `coding.rules.md`

  - Follow `## Organize Functions Into Logical Layers` in
    `.claude/skills/coding.rules.md`
  - Follow `## Order Layers by Abstraction Level` in
    `.claude/skills/coding.rules.md`
  - Follow `## Order Functions Within Each Layer` in
    `.claude/skills/coding.rules.md`
  - Follow `## Keep Related Functions Together` in
    `.claude/skills/coding.rules.md`
  - Follow `## Mark Private Functions` in `.claude/skills/coding.rules.md`


## Additional Guidance

- Avoid circular ordering where possible
- Preserve existing comments and docstrings
- Keep public entry points easy to locate near the end of the file
- Prefer cohesion and readability over strict categorization

# Constraints

## Preserve Behavior Exactly

- Do not modify functionality, logic, signatures, control flow, side effects, or
  semantics
- The resulting code must behave identically to the original

## Move Code Only

- The refactor must be structural only
- Allowed changes:
  - Reordering functions
  - Adding section headers
  - Renaming internal/private functions consistently
- Disallowed changes:
  - Rewriting logic
  - Simplifying implementations
  - Changing APIs
  - Changing imports unnecessarily
  - Modifying formatting beyond what is required for reorganization

# Verification
- [ ] Confirm every function from the original file is still present
- [ ] Run the file's unit tests to confirm behavior is unchanged
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall