infrastructure-audit

Audit Claude Code lab infrastructure for runtime, hook, script, and drift regressions.

9|Updated May 24, 2026
One-click install
npx skills add https://github.com/picmakpro/vibeflow-os --skill infrastructure-audit-picmakpro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infrastructure-audit
Source: https://github.com/picmakpro/vibeflow-os/tree/main/plugin/infrastructure-audit
Command: npx skills add https://github.com/picmakpro/vibeflow-os --skill infrastructure-audit-picmakpro

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, python3, jq, git, claude, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill detects silent regressions in a VibeFlow lab after Claude Code updates, including broken hooks, invalid settings, failing scripts, missing dependencies, unsupported runtime versions, and infrastructure drift.

Core Features & Use Cases

  • Runtime Auditing: Checks the Claude Code version, expected native tools, and supported runtime conventions.
  • Hook Validation: Verifies settings JSON, recognized lifecycle events, hook types, and referenced script paths.
  • Script Integrity Checks: Tests Bash syntax, executable permissions, required binaries, and available test suites.
  • Snapshot and Drift Detection: Creates infrastructure snapshots and compares them with previous baselines to identify regressions.
  • Use Case: Run the audit after a Claude Code update or periodically at session startup to identify infrastructure issues before they block development workflows.

Quick Start

Use the infrastructure-audit skill to inspect the current lab, report all runtime, hook, script, and drift findings, and generate a baseline snapshot.

Frequently Asked Questions about infrastructure-audit

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

FAQPage Schema
How do I detect infrastructure drift after a Claude Code update?

To detect infrastructure drift after a Claude Code update, you can run an audit that checks runtime versions, validates lifecycle hooks, verifies script integrity, and compares current infrastructure snapshots against previous baselines to identify silent regressions.

What is snapshot comparison for detecting runtime regressions?

Snapshot comparison for detecting runtime regressions involves creating a baseline of your current infrastructure settings and scripts, then comparing future states against this baseline to spot broken hooks, missing dependencies, or unsupported runtime versions.

Do I need bash and python3 to run infrastructure audits and script integrity checks?

Yes, you need bash and python3 to run infrastructure audits and script integrity checks. The audit also requires the Claude Code CLI, and validates jq and git as part of the audited toolchain to ensure complete infrastructure coverage.

When should I run an infrastructure audit to prevent development workflow disruptions?

You should run an infrastructure audit after a Claude Code update or periodically at session startup. Running the audit at these times identifies broken hooks, invalid settings, and missing dependencies before they silently block your development workflows.