BumpyClock/agent-templates / skills/engineering/change-amplification
change-amplification
UnverifiedFind PR change-amplification from missing owners/contracts; rank cleanup backlog.
Change Amplification
Find PRs showing change amplification: one intended change forced edits across multiple conceptually separate places because architecture lacked one clear owner, contract, or boundary.
Not a blame report or list of bad PRs. Output = ranked backlog of missing boundaries with PR links as evidence.
Inputs
Use PR history, current code, repo docs/tests. Prefer gh for PR data.
gh pr list --state merged --limit 100 --json number,title,url,body,mergedAt,files,additions,deletions
gh pr view <pr> --json number,title,url,body,files,commits,mergedAt
gh pr diff <pr> --patch
If target window, repo, or PR set unclear, ask or choose bounded recent window and say so.
Candidate Detection
Look for PRs where:
- one intended conceptual change appears in title/body,
- edits span conceptually separate layers or artifacts: source, tests, config, prompts, docs, generated code, scripts, migrations,
- repeated edits look like drift from a missing owner/contract/boundary,
- same invariant encoded in multiple places,
- tests had to change in many areas because no single contract captured behavior.
Reject PRs where breadth was justified:
- genuine cross-cutting feature,
- intentional broad refactor,
- generated/mechanical update only,
- migration that necessarily touches all call sites,
- formatting/rename-only breadth,
- one-time cleanup with no future leverage.
Verification Against Current Code
Before reporting candidate as actionable, verify suspected boundary gap still exists in current code.
- Inspect current files that carried the amplified change.
- Search for current owner/contract/type/test/lint rule that may already centralize the concept.
- If current code fixed the issue, mark
Resolvedor omit from actionable backlog. - If evidence incomplete, mark
Needs investigation, not actionable. - Include only actionable cleanups when current code still shows duplicated ownership, scattered invariant logic, weak contract, or missing guardrail.
Analysis Questions
For each verified candidate:
- Intended change: single conceptual change, usually from PR title/body.
- Amplification evidence: which files/tests/configs/prompts/docs had to change. Cite paths.
- Why architectural: why this wasn't ordinary feature breadth. Name missing boundary, owner, or contract.
- Better architecture: smallest change making next similar PR local.
- Mechanical prevention: what test, type, lint, schema, or contract check catches drift next time.
- Deletion criterion: what temporary compatibility path should be removed once new owner exists.
Ranking
Rank by expected future leverage:
- Frequency likely to recur.
- Number of concepts/files made local by the fix.
- Bug risk from duplicated invariants.
- Simplicity of cleanup.
- Existence of clear mechanical prevention check.
Do not over-rank speculative architecture rewrites. Prefer small owner/contract moves with obvious payoff.
Output
## Ranked Change-Amplification Backlog
### 1. <missing boundary / owner / contract>
- PR evidence: <PR title> <PR link>
- Intended change: <single conceptual change>
- Amplification evidence: <paths grouped by concept>
- Current-code validation: <what was checked; why issue still exists>
- Why architectural: <missing owner/contract/boundary>
- Better architecture: <smallest localizing change>
- Mechanical prevention: <test/type/lint/contract check>
- Deletion criterion: <compat path to remove later>
- Leverage: High | Medium | Low — <why>
## Rejected Candidates
- <PR link/title>: rejected because <genuine cross-cutting/refactor/resolved/etc.>
## Verification Notes
- Commands/data sources used.
- Limits or blind spots.
Findings evidence-backed. No private transcript paths, secrets, or unrelated personal data.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 192k | Updated | Claude CodeCodex | Verified | Install |