audit-modernization

Run a read-only modernization audit and write a dated Markdown report to /tmp.

3|1|Updated May 28, 2026
One-click install
npx skills add https://github.com/VMAFx/vmafx --skill audit-modernization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit-modernization
Source: https://github.com/VMAFx/vmafx/tree/main/.claude/skills/audit-modernization
Command: npx skills add https://github.com/VMAFx/vmafx --skill audit-modernization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a broad repository scan into a concise modernization audit so you can quickly see what remains stubbed, scaffolded, or deferred.

Core Features & Use Cases

  • Runs a read-only scan of the current tree and writes a dated Markdown report to /tmp.
  • Highlights stubs, deferred work, placeholders, implementation TODOs, and open state-file rows.
  • Helps with planning sessions, merge-train cleanup, and backlog reconciliation.

Quick Start

Use the audit-modernization skill to run the modernization audit on the current repository and save the report to /tmp.

Frequently Asked Questions about audit-modernization

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

FAQPage Schema
How do I audit a repository for stubs and deferred modernization work?

A repository modernization audit scans the current codebase tree to find scaffolded code, deferred work, and placeholder implementations, producing a dated Markdown report in /tmp to help you track what remains unfinished.

What is a modernization audit and when do I need to run one?

A modernization audit is a read-only repository scan that detects stubs, placeholders, and deferred work. You need to run one when preparing for planning sessions, cleaning up a merge train, or reconciling your development backlog.

Can I run a modernization audit on a local repository tree without modifying files?

Yes, the modernization audit runs with safe read-only execution on a local repository tree, scanning for stubs and deferred work while writing only to /tmp, ensuring your source files remain completely unmodified.

How do I generate a Markdown report of implementation TODOs and placeholders in my codebase?

You generate a Markdown report of implementation TODOs by executing a repository scan that targets placeholders, stubs, and open state-file rows, automatically writing a dated findings document to your /tmp directory.

Does the repository modernization audit require any specific dependencies or external components?

The repository modernization audit requires no external dependencies or components, needing only a local repository tree and the project_modernization_audit.py script to perform a read-only scan and output a Markdown findings report.