ftm-audit

Automate ftm-audit wiring checks from static analysis to runtime verification.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ftm-audit
Source: https://github.com/kkudumu/feed-the-machine/tree/main/ftm-audit
Command: npx skills add https://github.com/kkudumu/feed-the-machine --skill ftm-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires knip, and includes scripts (resource) and references (resource) components.

What problem does it solve?

ftm-audit automates and enforces wiring integrity across the full lifecycle of an FTM task—from static analysis to adversarial checks and automatic changelog updates—so teams ship reliable, wired code.

Core Features & Use Cases

  • Static Analysis with knip to detect unused files, exports, dependencies, and unreachable modules.
  • Adversarial audit across five wiring dimensions (import chains, rendering, routing, store reads, and API calls).
  • Auto-fix pipelines that generate fixes and a changelog, plus re-verification.
  • INTENT.md coverage checks to ensure documentation for new or changed functions, with module-level intents.
  • Blackboard state management integration to reflect task progress and decision history.

Quick Start

Run /ftm-audit after finishing a task to perform the full audit cycle: pattern detection, Layer 1 knip, 1.5 INTENT checks, 1.75 path resolution, Layer 2 adversarial audit, and Layer 3 auto-fix with re-verification; optionally perform Phase 3 runtime wiring if prerequisites are met.

Frequently Asked Questions about ftm-audit

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

FAQPage Schema
How do I automate end-to-end wiring audits for my codebase?

To automate wiring audits, run /ftm-audit to perform static analysis, adversarial checks across five wiring dimensions, and auto-fix pipelines with changelog generation. This verifies import chains, routing, rendering, store reads, and API calls end-to-end.

What is an adversarial wiring audit and when do I need it?

An adversarial wiring audit checks code integrity across import chains, rendering, routing, store reads, and API calls. You need it when shipping reliable, wired code that requires reproducible deployments and verified wiring contracts.

How do I check INTENT.md coverage for new or changed functions?

To check INTENT.md coverage, the audit verifies that documentation exists for new or changed functions alongside module-level intents. This ensures documentation requirements are met before deployment and tracks decision history.

Does knip work with automated auto-fix and re-verification pipelines?

Yes, knip is used for Layer 1 static analysis to detect unused files, exports, dependencies, and unreachable modules. The pipeline then applies adversarial audits, generates fixes with a changelog, and re-verifies the results automatically.

Can I use static analysis to auto-fix unused dependencies and generate a changelog?

Yes, the audit uses static analysis to detect unused dependencies and unreachable modules, then generates auto-fixes and a changelog. It re-verifies the fixes to ensure wiring integrity and reproducible deployments.

What are the limitations of automated wiring audits for runtime checks?

Automated wiring audits require prerequisites to be met for Phase 3 runtime wiring checks. Without these prerequisites, the audit focuses on static analysis and adversarial checks, potentially missing runtime-specific wiring issues.