organize-test

Organize Test Skill

Reorganize an existing Foundry test file (*.t.sol) so that imports, state variables, and functions follow the repository's established conventions. This skill makes purely structural changes — it never alters logic, assertions, values, names, or execution order.

---

0. Safety Guardrails — NEVER Violate

These rules are absolute. If any rule would be violated by a proposed change, skip that change entirely.

1. Scope: Only modify files matching *.t.sol inside contracts/tests/. NEVER touch production contracts or deploy scripts.
2. No semantic changes: Never modify function bodies, assertions, require/revert strings, call arguments, numeric values, or conditional logic.
3. No renames: Never rename functions, variables, contracts, structs, enums, events, or errors.
4. No additions or removals: Never add or remove imports, functions, state variables, or modifiers. Only reorder existing ones.
5. No visibility/type changes: Never change visibility (public/internal/private), mutability (constant/immutable), types, or inheritance lists.
6. Preserve comments: Move comments with their associated code. Never delete, rewrite, or add comments (except section dividers — see Section 5).
7. Preserve blank-line semantics: Keep logical blank-line separations inside function bodies untouched.
8. Skip if risky: If a reorganization is ambiguous, could affect behavior, or would produce a diff that is hard to review (>60% of lines changed), make the smallest safe change or do nothing.

---

1. Pre-Edit Checklist

Before making any edit, complete every item:

• Confirm the target file is *.t.sol under contracts/tests/.
• Read the entire file to understand its current structure.
• Identify the file type: Shared (Shared.t.sol), Concrete (concrete test), Fuzz (fuzz test), or Base (Base.t.sol, BaseFork.t.sol, BaseSmoke.t.sol).
• Check for any repo-specific conventions in the file that diverge from the defaults below. If present, respect the local convention.
• Plan all moves mentally before editing. Each move must be a pure relocation — same content, new position.