estate-rollout

Automate estate-wide repository migrations with dry-run diff verification.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/lucas42/lucos_claude_config --skill estate-rollout
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: estate-rollout
Source: https://github.com/lucas42/lucos_claude_config/tree/main/skills/estate-rollout
Command: npx skills add https://github.com/lucas42/lucos_claude_config --skill estate-rollout

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates coordinated changes across lucos repositories by validating changes with a dry-run diff before rollout, ensuring compliance before merge.

Core Features & Use Cases

  • Estate-wide convention updates and per-repo migrations
  • Dry-run diff auditing and gating before merge
  • Stepwise rollout with smoke tests and CI verification

Quick Start

Describe the change to be made and run the audit dry-run across all repositories to identify affected repos before performing the estate-wide rollout.

Frequently Asked Questions about estate-rollout

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

FAQPage Schema
How do I coordinate code migrations across multiple repositories?

To coordinate code migrations across multiple repositories, you can use an estate-wide rollout process that applies convention updates to each repo with staged steps and CI verification before merging.

What is a dry-run diff audit for repository changes?

A dry-run diff audit is a validation step that generates and verifies proposed changes across repositories without applying them, ensuring compliance and identifying affected repos before the actual migration.

How do I validate per-repo configuration updates before merging?

You validate per-repo configuration updates before merging by running a dry-run diff to audit the changes, performing smoke tests, and ensuring CI verification passes during a stepwise rollout.

Can I automate estate-wide convention updates with smoke testing?

Yes, you can automate estate-wide convention updates by orchestrating the migration in staged steps, executing smoke tests, and enforcing CI verification to ensure deployment completion before merging.

When should I use a stepwise rollout for repository migrations?

You should use a stepwise rollout for repository migrations when you need to update conventions or configurations in a coordinated, auditable fashion across an entire estate with validation gating.