purify

Remove dead code, redundant abstractions, and hygiene violations while preserving intended behavior.

1|Updated May 12, 2026
One-click install
npx skills add https://github.com/mystilleef/spae-framework --skill purify-mystilleef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: purify
Source: https://github.com/mystilleef/spae-framework/tree/main/skills/purify
Command: npx skills add https://github.com/mystilleef/spae-framework --skill purify-mystilleef

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebases accumulate dead code, over-engineered abstractions, duplication, and hygiene debt that increase maintenance cost and obscure intent. This Skill systematically eliminates KISS, YAGNI, Idiomatic, and Hygiene violations through a gated, verifiable workflow that never changes intended behavior. ## Core Features & Use Cases - Violation Detection: Surveys scoped code against a language-agnostic catalog of KISS, YAGNI, Idiomatic, and Hygiene violations, with optional fallow-based dead-code analysis for TypeScript/JavaScript diffs. - Safe Simplification: Removes dead code, inlines thin wrappers, merges duplicate paths, and simplifies conditions while keeping public interfaces and behavior stable. - Verified Cleanup: Runs tests after every change, audits its own git diff for self-introduced artifacts, and reverts to a known-good state if verification fails. - Use Case: After a feature sprint leaves behind unused helpers, commented-out blocks, and redundant wrappers, run this Skill on the changed files to strip the waste, confirm tests pass, and receive a terse report of every removal. ## Quick Start Ask the agent to purify the current uncommitted changes or a specific file path, for example by requesting a cleanup of the src/utils module.

Frequently Asked Questions about purify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I remove dead code safely without breaking behavior?▼

Run this Skill against a file path or your current uncommitted changes. It establishes a test baseline first, removes only verified dead code and redundant abstractions, reruns tests after each edit, and reverts to the last known-good state if anything fails.

What kinds of code violations does this refactoring detect?▼

It detects KISS violations like unnecessary abstractions, YAGNI violations like speculative features and dead code, non-idiomatic patterns, and hygiene debt such as cryptic names, debug artifacts, and commented-out code, using a language-agnostic violation catalog.

Does it work with TypeScript and JavaScript projects?▼

Yes. When the scope is current changes in a TS/JS project and the fallow tool is available, it runs a diff-based dead-code audit as an additional signal. All findings are treated as unverified candidates and confirmed by judgment before removal.

Can it change public interfaces or fix bugs it finds?▼

No. It preserves intended behavior and public interfaces unless you explicitly request an interface cleanup. A pre-existing bug exposed during cleanup is reported as a separate finding, and the edits that surfaced it are reverted.

What happens if tests fail during the cleanup?▼

The Skill backtracks to the last known-good state and retries. It never ends with a broken tree: either tests pass or the offending edits are reverted, and failures caused by its own edits are never treated as out-of-scope blockers.