principle-build-the-lever

Guides building rerunnable codemods, scripts, and generators instead of manual edits.

1|Updated Jul 5, 2026
One-click install
npx skills add https://github.com/yersonargotev/packy --skill principle-build-the-lever-yersonargotev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: principle-build-the-lever
Source: https://github.com/yersonargotev/packy/tree/main/bundle/skills/principle-build-the-lever
Command: npx skills add https://github.com/yersonargotev/packy --skill principle-build-the-lever-yersonargotev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hand-done edits, migrations, and analyses cannot be re-verified without redoing the work, leaving reviewers with nothing to rerun. This Skill enforces a working principle: for any non-trivial task, build a deterministic tool (codemod, script, generator, or delegate skill) that performs or proves the work, so the artifact itself becomes reviewable and rerunnable. ## Core Features & Use Cases - Lever-First Workflow: Do the first unit by hand to learn the recipe, then build the tool and prove it by diffing its output against the hand-done version. - Tool Selection Guidance: Choose codemods or scripts for edits, generators for repetitive files, dump-to-sqlite queries for analysis, and rerunnable checks for verification. - Subagent Coordination: When fanning work out to subagents, write the recipe, verification contract, and do-not-touch fences as a shared skill outside the delegates' write scope. - Use Case: While migrating hundreds of files to a new API, write a codemod, verify it against one hand-migrated file, rerun it across the codebase, and commit it so reviewers can rerun it instead of trusting manual edits. ## Quick Start Ask the agent to apply the build-the-lever principle to your current migration or refactoring task so it produces a rerunnable script instead of hand edits.

Frequently Asked Questions about principle-build-the-lever

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

FAQPage Schema
How do I automate repetitive code edits with a codemod?▼

Do the first edit by hand to learn the recipe, then write a codemod or script that applies the same transformation. Prove it by rerunning it on that first unit and diffing the output against your hand-done version before applying it everywhere.

When should I write a script instead of editing files by hand?▼

Build a tool for any non-trivial work, including one-off tasks where the script is what makes the work checkable. Skip it only for genuinely trivial changes, meaning a couple of obvious edits you can verify at a glance.

How do I keep subagents consistent when delegating repetitive tasks?▼

Write the recipe, verification contract, and do-not-touch fences as a single skill file that every subagent reads. Keep that file outside the delegates' write scope so they cannot quietly edit the shared contract.

What are the limitations of hand-done bulk changes?▼

Hand-done changes can only be re-verified by redoing them, giving reviewers nothing to rerun. A deterministic script turns trust into a rerunnable artifact, and a reviewer can check the work by executing the tool.

Should I commit the automation script after the task is done?▼

Commit the lever when the work outlives the session so the next run reruns it instead of redoing it. Keep the script minimal, building the smallest tool that does or proves the job rather than a framework.