audit-fleet

Compare per-repo configurations against declared fleet targets and output drift tables.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Cross-repo audits are needed to see which repos lag the standard; audit-fleet provides a read-only view of each repo's adoption status and drift against the fleet target, enabling teams to prioritize remediation.

Core Features & Use Cases

  • Per-repo drift reporting: compares actual repo config to fleet targets (baseline, profiles, and adoption tier).
  • Drift hotspots rollup: surfaces the biggest gaps to guide remediation priorities.
  • Read-only auditing: outputs a per-repo table and integrates with fleet-bootstrap for remediation planning.

Quick Start

Run a fleet-wide drift check against fleet.yml or explicit fleet lists to produce an actionable report.

Frequently Asked Questions about audit-fleet

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

FAQPage Schema
How do I check configuration drift across multiple repositories against a single standard?

To check configuration drift across multiple repositories, compare actual repo configurations against declared fleet targets. This read-only audit evaluates per-repo adoption, baselines, profiles, and versions to surface gaps against your standard.

What is fleet drift and how do I identify adoption gaps in my repos?

Fleet drift is the mismatch between declared fleet targets and actual repository configurations. You identify adoption gaps by running read-only audits that compare baseline, profiles, and tiers across repos against the fleet standard.

How do I prioritize remediation for cross-repo configuration drift?

Prioritize remediation for cross-repo drift by generating a drift hotspots rollup. This report surfaces the biggest configuration gaps, guiding teams on which repositories require immediate baseline updates.

Can I audit repo compliance without modifying any repository configurations?

Yes, you can audit repo compliance safely because the drift checking process is strictly read-only. It outputs a per-repo table of adoption statuses and configuration gaps without modifying your actual repositories.

How do I plan remediation after finding version and baseline drift in my repository fleet?

Plan remediation for version and baseline drift by integrating your per-repo audit report with fleet-bootstrap. This combination uses the identified drift hotspots to guide and execute necessary configuration updates across the fleet.