vc-prune

Name: vc-prune
Availability: InStock
Author: Vetcoders

Prune repositories to runtime and publish-cone surfaces with vc-agents.

1|Updated Mar 8, 2026

Search Tags:#automation #runtime #publish #repo #prune #cones #loct

Ready to run

npx skills add https://github.com/VetCoders/vibecrafted --skill vc-prune

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vc-prune
Source: https://github.com/VetCoders/vibecrafted/tree/main/skills/vc-prune
Command: npx skills add https://github.com/VetCoders/vibecrafted --skill vc-prune

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prune repositories to runtime and publish surfaces by stripping non-essential tooling, experiments, and dead code, ensuring the codebase ships with a lean, verifiable surface.

Core Features & Use Cases

Cone-driven pruning governance: define the runtime cone and the publish cone before proposing deletes.
External agent orchestration: utilize vc-agents for non-trivial prune tasks, pairing archaeologist with surgeon strengths.
Surface tightening with gates: run after-cut gates to tighten manifests, handlers, scripts, and env flags for a clean surface.
Proof-driven validation: require real proofs (smoke tests, imports, or publish-path checks) after pruning.

Quick Start

Tell VC to prune a repository by defining the cone and running the prune workflow to reduce surface area.

Frequently Asked Questions about vc-prune

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

FAQPage Schema

How do I prune a monorepo to its runtime or publish surface?▼

To prune a monorepo, you define the runtime or publish cone and run a prune workflow that strips non-essential tooling and dead code. This reduces the codebase surface area to a lean, deployable state.

What is a publish cone and when do I need it for large codebases?▼

A publish cone defines the exact code that must survive in a publish contract. You need it when pruning large codebases to strip experimental or dead code while ensuring the published package remains verifiable.

How do you validate a repository after pruning dead code?▼

After pruning dead code, you validate the repository using proof-driven checks like smoke tests, import verifications, or publish-path checks. This guarantees the remaining runtime surface functions correctly.

Can I automate non-trivial codebase pruning in large repositories?▼

You can automate non-trivial codebase pruning by orchestrating external vc-agents. These agents pair archaeological and surgical strengths to evaluate and strip non-essential files from large repositories.

What is the best way to tighten manifests and scripts after reducing repository surface area?▼

The best way to tighten manifests and scripts is by running after-cut gates. These gates clean handlers, scripts, and environment flags to ensure a verifiable surface after pruning.

Does vc-prune work for libraries that need strict runtime contracts?▼

Yes, vc-prune works for libraries by enforcing cone-based classification governed by runtime contracts. It strips non-essential code to ensure the library ships with a lean, verifiable publish surface.