skills.rest
VetCoders
VetCodersOFFICIAL
Explore all skills by this author →
WebsiteGitHub

vetcoders-prune

Identifies and removes non-runtime code, files, and directories from repositories using phased cleanup waves.

1|Updated Mar 8, 2026
Search Tags:#refactoring#codebase management#code cleanup#dead code removal#runtime analysis#repository pruning
One-click install
npx skills add https://github.com/VetCoders/vetcoders-skills --skill vetcoders-prune
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vetcoders-prune
Source: https://github.com/VetCoders/vetcoders-skills/tree/main/vetcoders-prune
Command: npx skills add https://github.com/VetCoders/vetcoders-skills --skill vetcoders-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the issue of bloated code repositories by systematically identifying and removing code, files, and directories that are not essential for runtime execution, thereby improving maintainability and reducing complexity.

Core Features & Use Cases

  • Runtime Cone Mapping: Identifies code strictly required for the application to run.
  • Classification: Categorizes files into KEEP-RUNTIME, KEEP-BUILD, KEEP-QA, MOVE-ARCHIVE, DELETE-NOW, or VERIFY-FIRST.
  • Phased Pruning: Executes cleanup in controlled waves, from disposable surface to unreachable product code.
  • Use Case: A large AI-generated project has accumulated significant cruft. Use this Skill to define the core runtime, archive experimental code, and delete obsolete tooling, resulting in a leaner, more manageable codebase.

Quick Start

Use the vetcoders-prune skill to identify and remove non-runtime code from the current repository.

Frequently Asked Questions about vetcoders-prune

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

FAQPage Schema
How do I remove dead code and non-runtime files from a bloated repository?▼

To remove dead code and non-runtime files, map the runtime cone to identify essential execution paths, classify artifacts into categories like KEEP-RUNTIME or DELETE-NOW, and execute phased cleanup waves to systematically prune deletable cruft.

What is runtime cone mapping for codebase cleanup?▼

Runtime cone mapping identifies the strict code paths required for an application to execute. It distinguishes essential runtime code from build dependencies, QA assets, and archival material, enabling targeted repository pruning without breaking functionality.

How do I clean up an AI-generated project that has accumulated cruft?▼

Clean up AI-generated project cruft by classifying files into runtime, build, QA, archive, and delete categories. Use phased pruning waves to safely remove obsolete tooling and experimental code, resulting in a leaner, maintainable codebase.

Can I use conservative pruning mode to safely reduce codebase complexity?▼

Yes, conservative pruning mode safely reduces complexity by classifying ambiguous files as VERIFY-FIRST rather than deleting them immediately. This controlled approach archives experimental code while protecting potentially essential runtime paths.

What's the best way to classify repository files for archival versus deletion?▼

Classify repository files by mapping the runtime cone and categorizing artifacts into KEEP-RUNTIME, KEEP-BUILD, KEEP-QA, MOVE-ARCHIVE, DELETE-NOW, or VERIFY-FIRST. This structural analysis distinguishes essential code from deletable cruft.

When should I not use automated repository pruning on my codebase?▼

Avoid automated repository pruning when file classification confidence is low or when untested code paths might be needed. Use radical pruning mode cautiously, as removing unverified files marked VERIFY-FIRST can break runtime execution.

Related Skills

Explore More Software Engineering Skills→
VetCodersVetCoders
1

loctree

Generate a holographic map of code structure, dependencies, and health.

Official
Advanced
minami110minami110
21

GDScript File Manager

Move, rename, or delete GDScript files with their .uid files.

Community
Basic
Destynova2Destynova2
5

cli-audit-tangle

Analyze codebases for god functions, circular dependencies, dead code, and module boundaries.

Community
Advanced
BamoseBamose
5

refactor-cleaner

Detect dead code and unused exports in TypeScript projects with knip, depcheck, and ts-prune.

Community
Advanced