skills.rest
rjwalters
rjwaltersCOMMUNITY
Explore all skills by this author →
GitHub

project-migrate

Migrate studio projects to the canonical post-#295 post-#296 project-org model.

1|Updated Nov 2, 2025
Search Tags:#rollback#canonical#legacy#atomic#anvil#studio#project-migration
One-click install
npx skills add https://github.com/rjwalters/bucket-brigade --skill project-migrate-rjwalters
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-migrate
Source: https://github.com/rjwalters/bucket-brigade/tree/main/.anvil/skills/project-migrate
Command: npx skills add https://github.com/rjwalters/bucket-brigade --skill project-migrate-rjwalters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Existing studio projects break silently after contract changes #295 and #296 because their on-disk layout no longer matches the canonical shape. This skill migrates them in place to the new model, preserving git history and operator-authored configuration.

Core Features & Use Cases

  • Shape detection and migration: Recognizes pre-#283 classic, post-#283 with .anvil.json, fully-migrated, and bare version-dir shapes, then applies atomic per-document migrations with rollback.
  • Single-file enrollment: Wraps loose .md or .tex files into project threads with surgical BRIEF.md appends that preserve every byte of operator config.
  • Foreign adoption: Adopts foreign vN report directories and letter-family IP threads into the canonical shape using declarative tag maps.
  • Honest review conversion: Converts foreign review.md stubs into recognizable unscored payloads without fabricating scores, and supports operator-driven LLM rescore in a second phase.
  • Use case: A research team migrating a portfolio of 50 legacy memo threads, deck threads, and proposal threads can run one command to converge everything onto the new contract while keeping existing git history intact.

Quick Start

Use the project-migrate skill to migrate the studio project located at ./my-project.

Frequently Asked Questions about project-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate legacy studio projects to a new on-disk layout without losing git history?▼

Migrate legacy studio projects to the canonical post-#295 form using a tool that applies atomic per-document migrations with rollback, preserving git history and operator-authored configuration intact during the layout conversion.

What is the best way to convert foreign review.md stubs into valid project payloads without fabricating scores?▼

Convert foreign review.md stubs into recognizable unscored payloads using honest review conversion, which avoids fabricating scores and supports operator-driven LLM rescore in a separate second phase after the initial migration.

How do I wrap loose markdown or tex files into a canonical project thread?▼

Wrap loose .md or .tex files into project threads using single-file enrollment, which surgically appends to BRIEF.md while preserving every byte of existing operator configuration within the canonical project-org model.

Can I test a project migration plan before applying changes to the on-disk layout?▼

Test a project migration plan using dry-run planning to preview how legacy .anvil.json threads and bare version-dir families will be adopted, ensuring strict post-apply verification passes before executing atomic apply with per-document rollback.

Why do existing studio projects break silently after contract changes #295 and #296?▼

Existing studio projects break silently because their legacy on-disk shape no longer matches the canonical post-#295 and #296 project-org model, requiring an in-place migration to converge the layout and restore strict contract verification.

Does project migration support idempotent re-runs for portfolios with mixed legacy shapes?▼

Project migration supports idempotent re-runs across mixed legacy shapes including pre-#283 classic layouts and post-#283 .anvil.json threads, allowing a portfolio of 50 memo, deck, and proposal threads to converge with one command.

Related Skills

Explore More Software Engineering Skills→
carson-sweetcarson-sweet
6

SweetClaude Setup

Detect project type and initialize standardized directory structures and configuration files.

Community
Advanced
growthxaigrowthxai

flow-conventions-folder-structure

Validate and fix Output SDK workflow folder structures.

Official
Advanced
danielgapdanielgap
4

pipeline-judge-dual

Merge dual-LLM evaluations into consolidated judge reports for business plans.

Community
Advanced
aalmadaaalmada
15

rollback-deployment

Roll back failed Azure Container Apps and Kubernetes deployments to previous revisions.

Community
Intermediate