skills.rest
arthur-debert
arthur-debertCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

migrate-consumer-to-build-dir

Migrate consumer repositories to the ADR-0001 .release/ build-dir with symlinks.

Updated May 1, 2026
Search Tags:#symlinks#lefthook#CI triage#release-sync#git migration#GitHub pull requests#ADR-0001
One-click install
npx skills add https://github.com/arthur-debert/release --skill migrate-consumer-to-build-dir
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migrate-consumer-to-build-dir
Source: https://github.com/arthur-debert/release/tree/main/skills/migrate-consumer-to-build-dir
Command: npx skills add https://github.com/arthur-debert/release --skill migrate-consumer-to-build-dir

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Migrating consumer repositories from an older in-place release-sync layout to the newer .release/ build-dir plus symlinks model (ADR-0001) without breaking canonical workflows, triggering CI drift, or producing irreproducible template changes.

Core Features & Use Cases

  • End-to-end consumer migration: Drives the full sequence to adopt the ADR-0001 layout, including running release-sync --migrate, setting up lefthook, committing with the canonical message, pushing the branch, and opening the PR.
  • Safety guardrails for repo state: Refuses to proceed when modified tracked files exist, avoids staging untracked scratch files, and ensures the release checkout is updated before migration to keep output reproducible.
  • CI triage and escalation boundaries: Stops when conflicts or canonical-lint drift is detected, and separates consumer-specific fixes from upstream release/ template fixes.

Quick Start

Ask the skill to migrate your consumer repository to the .release/ build-dir + symlinks model (ADR-0001) by running release-sync --migrate on that repo and preparing a PR ready for review and merge.

Frequently Asked Questions about migrate-consumer-to-build-dir

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

FAQPage Schema
How do I migrate a repository to the release-sync build-dir layout?▼

To migrate a repository to the release-sync build-dir layout, you run the release-sync --migrate command on a clean branch. This automates the transition to the ADR-0001 .release/ build-dir plus symlinks model and prepares a ready-to-merge PR.

What is the .release/ build-dir and symlinks model?▼

The .release/ build-dir and symlinks model is an ADR-0001 standard layout that moves release artifacts into a dedicated directory. It replaces older in-place release-sync layouts to prevent CI drift and ensure reproducible template changes.

How do I re-synchronize a stale release-sync migration PR?▼

You re-synchronize a stale release-sync migration PR by running the migration sequence again on a clean checkout. The process resets the branch and re-applies the release-sync --migrate command to update the build-dir layout.

Can I run release-sync migration with uncommitted changes in my repository?▼

You cannot run release-sync migration with uncommitted changes. The process includes safety guardrails that refuse to proceed if modified tracked files exist, ensuring a clean checkout for reproducible migration output.

What happens if canonical-lint drift or conflicts are detected during git migration?▼

If canonical-lint drift or conflicts are detected during git migration, the process stops automatically. This CI triage boundary prevents breaking canonical workflows and separates consumer-specific fixes from upstream release template fixes.

Does the build-dir migration use git add -A for staging files?▼

The build-dir migration does not use git add -A for staging files. It uses guarded git staging to avoid committing untracked scratch files, ensuring only the intended release-sync template changes are committed.

Related Skills

Explore More Software Engineering Skills→
biz-Streambiz-Stream

create-release

Create a Git release tag, push it to origin, and trigger the GitHub release workflow.

Official
Advanced
paulnsorensenpaulnsorensen
15

affinage

Triage pull request review comments, CI failures, and merge conflicts into graded reports.

Community
Advanced
holger1411holger1411
70

qa

Run lint, format, TypeScript, and build checks on AstroDeck projects.

Community
Advanced
EdgeAppEdgeApp
1

staging-cherry-pick

Cherry-pick non-merge commits from pull requests onto a staging branch.

Official
Advanced