repo-revamp repo-revamp v1.0.1

Claude Code plugin

Turn a repository into a live, documented, search-indexed site.

repo-revamp is the playbook that takes a GitHub repository from "here is an old repo" to a verified public site, without changing the product.

InstallQuick startRead the source

What it does

Most repositories are judged in the first minute: by the README, by the demo, by whether a search engine can find them at all. A revamp fixes that surface. It is also the kind of work that quietly breaks things, because the person doing it is editing the same repository the product lives in.

repo-revamp turns the work into a playbook with a state machine. A read-only recon establishes the facts. A numbered spec asks the owner the decisions that matter, one recommendation per question. One delegated agent builds a generated site in docs/ behind a deterministic builder and a set of hard gates. The orchestrator verifies every claim itself, deploys on the owner's go, and records what it learned.

The product is frozen throughout. A presentation-only revamp may change the README, the site, the builder, the requirements file, the site workflow and an append-only .gitignore. A boundary diff proves it: if the diff prints a product path, the pull request is out of scope.

The phase state machine

Every revamp moves through eight phases in order. A phase's exit gate must be green before the next one starts, and the state file records where the work stopped, so a fresh session resumes instead of starting over.

The repo-revamp phase state machine Eight phases in order: INTAKE, SPEC, BUILD, REVIEW, DEPLOY, SEO, SHIP and CLOSE. Each phase box carries its exit gate underneath: RECON.md exists, USER DECISIONS recorded, gate green and draft PR open, V1 to V16 green, live URLs answer, sitemap submitted, merged on the owner's go, tracker and handoff updated. Arrows connect the phases in sequence. The phase state machine A phase's exit gate must be green before the next phase starts. INTAKE phase 0 read-only recon EXIT GATE RECON.md exists SPEC phase 1 numbered questions EXIT GATE USER DECISIONS recorded BUILD phase 2 one delegated agent EXIT GATE gate green, draft PR open REVIEW phase 3 the orchestrator verifies EXIT GATE V1–V16 green continues DEPLOY phase 4 coordinator and owner EXIT GATE live URLs answer SEO phase 5 sitemap and metadata EXIT GATE sitemap submitted SHIP phase 6 on the owner's go EXIT GATE merged on the owner's go CLOSE phase 7 record and hand off EXIT GATE tracker and handoff updated phase exit gate next phase

Scroll the diagram sideways to see all of it.

The eight phases and the exit gate that closes each one.

Text alternative: INTAKE closes when RECON.md exists; SPEC when the owner's USER DECISIONS are recorded; BUILD when the local gate is green and a draft pull request is open; REVIEW when the V1 to V16 checks are green; DEPLOY when the live URLs answer; SEO when the sitemap is submitted; SHIP when the merge happens on the owner's explicit go; CLOSE when the tracker and the handoff are updated.

The state file is _revamp/<repo>/STATE.md. It holds the phase, the branch, the head, the gates, the open questions and the next action. The revamp-status command prints it in five lines, which is what a resumed session reads first.

What the plugin ships

The repository is small on purpose. The depth lives in the reference files, which are read one phase at a time rather than all at once. The skill is the contract; the references carry the detail; the commands start each part of the work; the agents do the delegated work; the scripts verify and inventory.

The repo-revamp component map The plugin at the centre, surrounded by the parts it ships: one skill, 17 reference files, 7 templates, 5 commands, 3 agents, 3 scripts, the danube-labs marketplace, and the host that serves the generated site. The host is drawn with a dashed border because it is external to the repository. What the plugin ships One repository, one marketplace entry, one generated site. repo-revamp Claude Code plugin skill SKILL.md 17 references 00 to 16 7 templates state, spec, briefs 5 commands slash commands 3 agents build, recon, verify 3 scripts verify, inventory, validate marketplace danube-labs host GitHub Pages in the repository external host belongs to the plugin

Scroll the diagram sideways to see all of it.

The plugin's parts, and the one external piece: the host that serves the generated site.

Text alternative: At the centre is the repo-revamp plugin. Around it: one skill file, 17 reference files numbered 00 to 16, 7 templates for state, spec, briefs, the pull request body, the verify recipe and the managed CLAUDE.md block, 5 slash commands, 3 agents for building, recon and verification, 3 scripts for verification, screenshot inventory and plugin validation, the danube-labs marketplace entry, and the external host, GitHub Pages.

A real run

The capture below is the output of claude plugin details repo-revamp on a machine where the plugin is installed. It is not a mock: the component inventory and the token estimates come from the installed plugin. The inventory lists six skills: repo-revamp itself and the five commands.

Terminal output of claude plugin details repo-revamp, listing version 1.0.1, six skills, three agents, no hooks or MCP servers, and the per-component token estimates.
The installed plugin's own inventory: six skills, three agents, and the token cost it adds to every session.

The projected token cost is the plugin's always-on cost, not the cost of a revamp. A revamp session reads a few reference files and runs commands; the always-on figure is what every session pays for having the plugin installed.

Verified quick facts

Every number below is computed from the repository by the site builder, not typed by hand. The claims ledger behind this page records the evidence for each one.

Version
1.0.1
Licence
MIT
Reference files
17
Templates
7
Commands
5
Agents
3
Scripts
3
Markdown lines
3489
Python lines
637
Requires
Claude Code, git, gh, Python 3.12

Install

One command installs the plugin from the marketplace in this repository:

Claude Code
/plugin install repo-revamp --marketplace FiredMosquito831/repo-revamp

Or add the marketplace first and install from it by name. Both routes are in the install guide, together with the requirements and what a working install looks like. Nothing is installed globally, and no configuration file is edited by hand.

Install guideQuick start

Questions people ask first

Does it change my product code?

No. A presentation-only revamp may change the README, the site, the builder, the requirements file, the site workflow and an append-only .gitignore. The boundary diff must print nothing else, and a product change is a stop-and-report event.

What does it need?

Claude Code with plugin support, git, an authenticated gh for the GitHub steps, and Python 3.12 for the scripts. The screenshot clustering needs Pillow and imagehash in a scratch environment, never in the repository.

What happens when a fact cannot be verified?

It is cut. Every factual statement on a generated page needs a row in the claims ledger with evidence that resolves to a file in the repository. A number that appears in no source is a bug, not a rounding decision.

The FAQ answers more, including how long a revamp takes, what it costs to run and what it cannot do.

Read the FAQ

Where to go next