one-change-at-a-time

SKILLWorkflowcommunity
v0.0.0tedgoldsteinMITUpdated 3mo agoSource →

When debugging or fixing a regression, isolate variables. Don't combine "I upgraded the dep AND refactored AND added a feature" in one commit / PR / deploy. The cost of bundling is exponential in the number of bundled changes — every interaction has to be considered. The cure is discipline at scope

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
1Clients
1Formats
3mo agoLast update
Skill
Authortedgoldstein
Version0.0.0
LicenseMIT
CategoryWorkflow
Formatsskill.md
PromptNot published
Compatibility
Claude✓ Supported
Cursor—
Copilot—
ChatGPT—
Gemini—
About

When debugging or fixing a regression, isolate variables. Don't combine "I upgraded the dep AND refactored AND added a feature" in one commit / PR / deploy. The cost of bundling is exponential in the number of bundled changes — every interaction has to be considered. The cure is discipline at scope boundaries (commit, PR, deploy).

Keywords
skillclaude

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.