principle-build-the-lever

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

1|Updated Aug 27, 2025
One-click install
npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill principle-build-the-lever-igorganapolsky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: principle-build-the-lever
Source: https://github.com/IgorGanapolsky/Random-Timer/tree/main/.cursor/skills/principle-build-the-lever
Command: npx skills add https://github.com/IgorGanapolsky/Random-Timer --skill principle-build-the-lever-igorganapolsky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Non-trivial work done by hand is slow, inconsistent, and impossible for a reviewer to re-verify without redoing it. This Skill enforces a working principle: for any non-trivial task, build a deterministic tool (codemod, script, generator, or delegate skill) that does or proves the work, so the artifact itself can be rerun and reviewed. ## Core Features & Use Cases - Lever-First Decision Rule: Apply to edits, migrations, analyses, and checks; skip only when the task is trivial and verifiable at a glance. - Prove-by-Rerun Workflow: Do the first unit by hand, build the tool, then diff its output against the hand-done version to validate correctness. - Delegation Contract: When fanning work out to subagents, encode the recipe, verification contract, and do-not-touch fences in a skill file outside the delegates' write scope. - Use Case: When migrating hundreds of files to a new API, write a codemod, rerun it on a hand-converted sample to confirm identical output, and commit the script so reviewers can rerun it. ## Quick Start Ask the AI to apply the build-the-lever principle to your next migration or bulk edit so it produces a rerunnable script instead of manual changes.

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. Rerun it on that first unit and diff against your manual version to prove correctness before running it on everything.

When should I write a script instead of editing files manually?

Write a script whenever the work is non-trivial: bulk edits, migrations, analyses, or checks a reviewer must re-verify. Skip the tooling only for trivial changes, a couple of obvious edits you can confirm at a glance.

How do I keep subagents consistent when delegating bulk work?

Write the recipe, verification contract, and do-not-touch fences into a single skill file that all delegates read. Keep that file outside the delegates' write scope so they cannot quietly modify the contract.

What are the limitations of hand-done bulk changes?

Hand-done changes can only be re-verified by redoing them, so reviewers must trust the author. A deterministic script turns verification into rerunning one artifact, and it applies the change identically every time.

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

Commit the script when the work outlives the session, so future contributors can rerun or adapt it. Keep it minimal: the smallest script that does or proves the job, never a framework.