code-cleanup

Files (2)

• SKILL.md
• code-cleanup.md

SKILL.md (first lines)

# Skill: code-cleanup

Invoked by: `/code-cleanup` command (a.k.a. **Code Cleanup**)

## Procedure

Load and follow `skills/code-cleanup/code-cleanup.md` when executing this skill.

## Purpose
Review a repository for cleanup and re-organize it to a professional, industry-standard
layout **without impacting or breaking any functionality or capabilities**. Files that are
no longer necessary are *archived* (moved to `archive/`), never deleted, so anything can be
restored if an issue surfaces. Duplicates, redundancies, and trailing artifacts are
consolidated, files are moved to appropriate folders, and the result is documented so a
developer or agent can understand the codebase.

## When to Use
- The repo has accumulated stray files, scratch scripts, duplicate configs, or ad-hoc folders
- Before a release or handoff, to present a clean, navigable structure
- After a burst of rapid iteration that left the tree disorganized
- Anytime the user asks to "clean up", "re-organize", or "tidy" the codebase

## Output
- A **cleanup plan** (proposed moves/archives/consolidations) presented for review before changes
- Files moved to appropriate folders; obsolete-but-restorable files relocated to `archive/` with a manifest
- Updated comments / READMEs so structure is self-explanatory
- A verification report confirming **no functionality changed** (references checked, tests run)
- A list of **efficiency improvements** to apply *after* cleanup (recommendations only, not applied)

## Safety Contract (Never Break Functionality)
- **Archive, don't delete.** Obsolete files move to `archive/` preserving their relative path.
- **Impact-gate every move.** Run `gitnexus_impact({target: "<symbolOrModule>", direction: "upstream"})`
  before relocating any code file. Report blast radius. **HIGH or CRITICAL risk → stop and warn the user;
  do not move.** For non-code files (docs, configs, assets), use `git grep -n "<filename>"` to find references.
- **Moves use the call graph.** For code symbols, prefer `gitnexus_rename` / refactoring-aware moves so
  imports update; never blind find-and-replace.
- **Verify after each batch.** Run `gitnexus_detect_changes()` and the test suite; only proceed if scope
  matches intent.
- **No behavior edits.** This skill moves, consolidates, and documents — it does not refactor
  logic. Logic improvements are *noted*, not applied.

## Harness References
- Procedure: `skills/code-cleanup/code-cleanup.md`
- Impact analysis: `.claude/skills/gitnexus/gitnexus-impact-analysis/SKILL.md`
- Refactoring (safe moves/renames): `.claude/skills/gitnexus/gitnexus-refactoring/SKILL.md`
- Validation: `skills/validate/validate.md`, `scripts/07-validate-harness.sh`
- Commit (optional, after approval): `skills/commit/` (`/gitcommit`)
- Archive location: `archive/` (repo root)

## Autonomy Mode Recommendation

When running cleanup workflows via orchestrator:

```bash
python3 scripts/orchestrate.py route iteration --execute --adapter cli --autonomy cautious
```

**Cautious mode** is recommended for cleanup workflows because:
- Auto-approves LOW/MEDIUM risk operations (file moves, archive operations)
- Prompts for HIGH risk operations (large refactors, breaking moves)
- Blocks CRITICAL operations (force operations, mass deletions)

Review `runs/autonomy-decisions.jsonl` after completion to verify appropriate risk classifications.

## Next Step
- Success: run `/validate` (or the project test suite) to confirm health, then commit on a branch.
- If impact analysis flags HIGH/CRITICAL risk: stop, report blast radius, and hand back to the user for a decision.

From 3rdAI-admin/th3rdai-harness, MIT.

More from 3rdAI-admin/th3rdai-harness