audit-config

Audit Octopus configuration files for drift, missing triggers, and deprecated paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a pre-merge audit of the Octopus configuration surface, surfacing model-specific assumptions, stale references, skills without triggers, and deprecated paths to ensure configuration quality and safety before changes are merged.

Core Features & Use Cases

  • Inventory and evaluate the configuration surface across rules/, skills//SKILL.md, hooks//.sh, commands/**/.md, and bundles/**/*.yml.
  • Produce a severity-weighted report (block/warn/info) to guide remediation before merges.
  • Trigger reviews automatically on edits to the configuration surface to maintain repository health.

Quick Start

Run the audit-config check to generate a configuration health report for the current branch.

Frequently Asked Questions about audit-config

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

FAQPage Schema
How do I audit Octopus configuration files for stale references and deprecated paths?▼

Run a configuration audit across rules, skills, hooks, commands, and bundles to detect model drift, stale references, and deprecated paths before merging changes.

What is a pre-merge configuration quality audit for Octopus?▼

A pre-merge configuration audit evaluates the Octopus configuration surface for model-specific assumptions, phantom skills, and untouched hooks to produce a severity-weighted remediation report.

How do I check for missing triggers and phantom skills in Octopus bundles?▼

Inventory and evaluate files under skills/**/SKILL.md and bundles/**/*.yml to identify missing triggers, phantom skills, and configuration drift across the repository.

When should I run an Octopus configuration audit?▼

Run an Octopus configuration audit during quarterly reviews or immediately after model-family changes to catch untouched hooks, deprecated paths, and maintain repository health.

Does the Octopus configuration audit require access to specific metadata directories?▼

Yes, the audit requires access to metadata across rules/, skills/**/SKILL.md, hooks/**/*.sh, commands/**/*.md, and bundles/**/*.yml to accurately evaluate the configuration surface.