fleet-bootstrap

Generate per-repo .octopus.yml manifests from a single fleet.yml.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill fleet-bootstrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fleet-bootstrap
Source: https://github.com/leocosta/octopus/tree/main/skills/fleet-bootstrap
Command: npx skills add https://github.com/leocosta/octopus --skill fleet-bootstrap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fleet-wide standardization of repository configurations by generating per-repo .octopus.yml from a single fleet.yml, enabling consistent policy, layered stacks, and safe adoption.

Core Features & Use Cases

  • Consolidates baseline, stack profiles, and adoption tiers into per-repo manifests
  • Supports multi-stack and legacy repos with dry-run and guarded promotion
  • Integrates with audit-fleet and octopus setup to roll out changes

Quick Start

Run octopus fleet-bootstrap to compose fleet.yml into per-repo .octopus.yml and preview changes before applying.

Frequently Asked Questions about fleet-bootstrap

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

FAQPage Schema
How do I standardize configuration files across a multi-repo software fleet?

Standardize a multi-repo fleet by generating per-repo .octopus.yml manifests from a single fleet.yml file. This consolidates baseline settings, stack profiles, and adoption tiers into consistent per-repo configurations.

Can I preview configuration changes before applying them to my repositories?

Yes, you can preview configuration changes using the dry-run mode to compose diff previews. This allows you to review staged adoption tiers and safely merge keys before applying updates via octopus setup.

How do I safely roll out standardization to legacy repositories with different stacks?

Safely roll out standardization to legacy repositories using staged adoption tiers (T0/T1/T2) and dry-run previews. This guarded promotion approach safely merges keys and avoids destructive pushes across multi-stack fleets.

What is the best way to audit a software fleet before applying standardized manifests?

The best way to prepare for fleet standardization is integrating with audit-fleet to assess repository states. After auditing, compose a single fleet.yml to generate per-repo .octopus.yml manifests for consistent policy enforcement.

Does fleet-bootstrap support safe merging to avoid overwriting existing repository configurations?

Yes, fleet-bootstrap supports safe merging of configuration keys to avoid destructive pushes. It safely merges keys from your fleet.yml into existing per-repo .octopus.yml files without overwriting unmanaged settings.