code-scaffold-backport
/code-scaffold-backport
Back-port an instance fix into the generator that produced it — cookiecutter, scaffold, `new-*` recipe. Use when fixing, reviewing, or auditing a generated file.
- Author
- laurigates ↗
- Repository
- claude-plugins ↗
- Licence
- MIT
- Last repository change
- 24.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 24.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Back-port an instance fix into the generator that produced it — cookiecutter, scaffold, `new-*` recipe. Use when fixing, reviewing, or auditing a generated file.
Original author description
Back-port an instance fix into the generator that produced it — cookiecutter, scaffold, `new-*` recipe. Use when fixing, reviewing, or auditing a generated file.
How it works
- When to Use This Skill
- The failure mode
- The rule
- Where generators hide
- Verify
- Rationale
SKILL.md preview
--- name: code-scaffold-backport description: Back-port an instance fix into the generator that produced it — cookiecutter, scaffold, `new-*` recipe. Use when fixing, reviewing, or auditing a generated file. allowed-tools: Read, Grep, Glob, Edit, Bash, TodoWrite created: 2026-08-19 modified: 2026-08-19 reviewed: 2026-08-19 --- # Back-Port Instance Fixes Into Their Scaffold/Generator ## When to Use This Skill | Situation | Skill | |-----------|-------| | Fixing, reviewing, or auditing a file a generator emitted — cookiecutter/copier template, justfile `new-*` recipe, a `*-scaffold` skill, a "copy the example app" doc | **This skill** — patch the generator in the same sweep | | Repeated code inside one codebase, with no generator behind it | `code-quality-plugin:dry-consolidation` | | Auditing a whole fleet of generated instances against their template | The inverse direction — `.claude/rules/generated-fleet-drift.md`; an instance may legitimately be *ahead* of the template, so never auto-apply template → instance | When fixing something that was *generated* — a site scaffolded by a justfile recipe, a repo from a cookiecutter template, a config from a `new-*` skill — check whether the bug came from the generator, and if so, fix the generator **in the same sweep**. A fix applied only to the deployed instance leaves every future generation broken in the same way, and the gap is invisible until the next person scaffolds. ## The failure mode Canonical case (FVH `sites` monorepo, 2026-06): two PRs fixed the deployed `example-static` site — `service.targetPort: 8080` for the non-root nginx image, numeric `runAsUser` for Kyverno — but the `just new-site` template that had produced those broken values was never touched. Every subsequently scaffolded site would have shipped with chart-default port-80 probes against an 8080 listener: pod never Ready, stuck `Progressing`, no error anywhere. Found and back-ported only weeks later during a readiness audit (sites#11). The shape is always the same: 1. An instance misbehaves; someone fixes the instance. PR merges, done. 2. The generator still emits the pre-fix content. 3. The next generation reproduces the bug — often for someone without the context of fix #1. ## The rule - **When fixing a generated artifact**, ask: "did the generator produce this bug?" If yes, patch the generator template in the same PR (or an immediately linked one) — not as a someday follow-up. - **When reviewing a fix to a known-scaffolded file** (e.g. `deploy/values.yaml` in a monorepo with a `new-*` recipe, anything under a directory a cookiecutter emits), check the template for the same defect before approving. - **When auditing a scaffold for readiness**, diff the template's output against the oldest working instance — accumulated instance-only fixes show up as the delta. ## Where generators hide - justfile `new-*` recipes with heredoc templates - `cookiecutter/` directories and copier templates - Claude skills that scaffold (`*-scaffold`, `configure-*`) - "Copy the example app" docs — the example *is* the generator; fixes to forks of it don't propagate back ## Verify After back-porting, generate a throwaway instance and diff it against the fixed real instance — the relevant blocks should match: ``` just new-site zz-smoke-test diff <(yq ... sites/zz-smoke-test/deploy/values.yaml) <(yq ... sites/example-static/deploy/values.yaml) ``` Clean up the throwaway (including any registry/config files the recipe mutated) before committing. ## Rationale This is DRY applied to provenance: the template is the source of truth for new instances, so a fix that skips it creates a silently diverging copy. The cost asymmetry is stark — back-porting at fix time is one extra edit with full context in hand; discovering it later costs a broken deploy, a re-diagnosis from scratch, and usually a different person's afternoon.
Versions
The database has no other skills named code-scaffold-backport.
Database snapshot: 13.11.2026 · package version 332cd02ac585 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100backport-pr
Backports a merged PR to a release branch by triggering the /backport bot, waiting for the bot-created PR, and filling in the shiproom template (Customer Impact, Testing, Risk, Regression?). Use when asked to: backport a PR, port a fix to a release branch, fill in a backport… - 100pr-backport
Backport a merged PR to a release branch. Use this when you need to cherry-pick a fix or feature into an older branch. - 100backport
Use this skill when backporting a merged CPython change to a maintenance branch (3.14, 3.13, etc.) - whether invoked as /cpython:backport <version> [PR], asked to backport or cherry-pick a fix from main, or handling a failed automated miss-islington backport. Produces a… - 100backport-pr
Backport a merged PR to a maintenance major branch (v10 by default) in getsentry/sentry-javascript. Cherry-picks the PR's squash-merge commit onto the target branch, namespaces the commit/PR title scope (e.g. fix(core) -> fix(v10/core)), opens a draft backport PR, and documents… - 100git-backport
Back-port a specific commit from master to a release branch via cherry-pick. Creates a dedicated backport branch, attempts the cherry-pick, pushes it, and opens a PR by default. Returns to the original branch when done (success or failure). If there are merge conflicts,… - 100backport
Backport a merged CocoIndex pull request from main to a release branch (release/X.Y) so that it ships in the next patch release: decide whether it qualifies, cherry-pick with -x in a scratch worktree, resolve conflicts, and land it through a pull request to the release branch.…