agentsclimarketplace

Retrofit skill

Skill joseluisamado/bootstrap-project-skill/retrofit-skill

A Claude Code skill that crystallizes a project-design conversation into a complete project scaffold.

Install
npx -y skills add joseluisamado/bootstrap-project-skill --skill retrofit-skill

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Reshape an existing project to the bootstrap-project skill standard without losing content, history, or working code. Walks the repo, classifies every file as missing / present-template-shape / present-bespoke / empty-placeholder, asks the same five spec questions as bootstrap-project (plus a content-strategy question), reshapes the docs quintet, backfills CHANGELOG from git history, moves files with reference-updating, and marks the project with `.bootstrap-meta.yaml` mode: retrofit. Use this when the user says "retrofit this project", "bring this repo up to the bootstrap-project standard", "reshape this to skill shape", or invokes /retrofit-project. Like bootstrap-project, it is a finalizer — it assumes the analysis conversation has happened in this session and extracts spec from context. Unlike bootstrap-project, it does NOT refuse on non-empty projects — that is its entire reason to exist. Do NOT use this for: greenfield projects (use /bootstrap-project instead); projects without a `.git/` directory (the CHANGELOG backfill and the "everything is in git" safety net require git history); already-bootstrapped projects whose `.bootstrap-meta.yaml` reports the same skill version (no work to do — say so and stop).

SKILL.md

3.5 KB, 515 tokens by cl100k_base, as published. Nobody here has run it

retrofit-project

This skill produces the same end-state as bootstrap-project (same templates, same canonical shape) on a repo that already has content. The hard part is not the writing — it is the negotiation with what is already there: preserving facts under reshape, finding canonical homes for bespoke content, moving files without breaking references, and being explicit about what was deleted and why.

The full playbook lives in INSTRUCTIONS.md. Read it when the skill is invoked. The short version:

  1. Refuse if invoked cold or on a non-git repo. Need analysis context and a git safety net.
  2. Inventory diff. Walk every always-present file from the bootstrap spec; classify as missing / present-template-shape / present-bespoke / empty-placeholder. Print the table.
  3. Extract spec from conversation — same fields as bootstrap-project (project_name, principles, milestones, stack_profile, deploy_model, audience, license, add-ons), plus content-preservation strategy.
  4. Confirm the plan in one block: what gets written, rewritten, moved, deleted. Wait for "go."
  5. Execute in this order: (a) write missing always-present files; (b) rewrite bespoke docs to canonical shape, preserving content; (c) move files with reference-updating sub-passes; (d) delete with explicit justification; (e) backfill CHANGELOG from git tag + git log + any existing PROGRESS versioning table; (f) write .bootstrap-meta.yaml with mode: retrofit.
  6. Generate BOOTSTRAP-MANIFEST.md with the richer retrofit shape: files written / rewritten / moved / deleted / preserved unchanged.
  7. Final compliance review. Cross-ref check, no-clobber check, no-forbidden-file check. Print the "next 30 minutes" punch list.

The skill shares templates/ with bootstrap-project — same renderers, same conditional flags. Don't duplicate.

The skill never deletes silently. Every deletion appears in the confirmation block before execution and in the manifest after.

For background on why retrofits are not just "bootstrap on a dirty directory," see patterns/why-retrofit-is-different.md.

What ships with it: 2 files

27.7 KB alongside SKILL.md

patterns/

Keep looking

Skills are one crate of 326,970. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.