safe-cleanup

name	safe-cleanup
description	Performs one evidence-backed, behavior-preserving source cleanup at a time. Use when the user asks to remove a concrete duplication, dead indirection, oversized responsibility, or similar maintainability problem without changing observable behavior.
license	MIT
compatibility	Pi skill for a trusted writable Git worktree with project-defined verification commands.
metadata	{"version":"1"}

Safe Cleanup

Purpose

Complete exactly one bounded cleanup target while preserving observable behavior. Prefer a small deletion or simplification over a new abstraction, configuration option, framework, or broad rewrite.

This skill provides a workflow, not a repository scanner. Do not import or recreate OMP-specific clone, god-object, dead-export, deep-import, or defensive-check scanners.

Preconditions

Before editing:

1. Read the applicable repository instructions and owner documentation.
2. Inspect the current branch, worktree, and target files. Preserve unrelated and pre-existing changes.
3. Restate one concrete cleanup target and the observable behavior that must remain unchanged.
4. Identify the exact baseline test command. If no meaningful observable check exists, define the smallest one before cleanup.