af-maintenance

Scan TypeScript/JavaScript projects for structural issues, dead code, and terminology drift.

3|Updated Oct 5, 2025
One-click install
npx skills add https://github.com/korchasa/ide-rules --skill af-maintenance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: af-maintenance
Source: https://github.com/korchasa/ide-rules/tree/main/catalog/skills/af-maintenance
Command: npx skills add https://github.com/korchasa/ide-rules --skill af-maintenance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes a rigorous 7-point maintenance sweep to identify structural deviations, documentation inconsistencies, dead code, complexity hotspots, technical debt, missing code documentation, and terminology drift. All findings are actionable and saved to a whiteboard report.

Core Features & Use Cases

  • End-to-end maintenance workflow that scans project structure, source, tests, and documentation.
  • Threshold-based indicators (e.g., large files, long functions, pervasive TODOs) aggregated into a structured, actionable report.
  • Actionable remediation guidance tracked through a task-management style workflow and captured in the whiteboard.md artifact for team visibility.

Quick Start

Run the full 7-point maintenance sweep and save the report to whiteboard.md.

Frequently Asked Questions about af-maintenance

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

FAQPage Schema
How do I audit codebase health and identify technical debt in a TypeScript project?

You can identify technical debt by running a maintenance sweep that scans source and test directories for TODOs, complexity hotspots, and dead code, aggregating threshold-based findings into a structured health report.

What is the best way to track TODOs and terminology drift across source and documentation?

The best way to track TODOs and terminology drift is a maintenance sweep that scans source and documentation directories, detecting inconsistencies and aggregating threshold-based findings into a structured health report.

Does the codebase maintenance sweep work without external dependencies?

The maintenance sweep operates with no dependencies, requiring only a TypeScript or JavaScript project containing src, docs, and test directories to execute its end-to-end structural and hygiene analysis.

How do I generate a code quality report and save it for team visibility?

You generate a code quality report by running the maintenance sweep, which evaluates threshold-based indicators like large files and long functions, saving actionable remediation guidance directly to a whiteboard.md artifact for team visibility.

When do I need an end-to-end code hygiene sweep instead of a basic linter?

You need an end-to-end code hygiene sweep when your project suffers from structural deviations, missing documentation, and terminology drift across code and docs, which a basic linter cannot detect or aggregate into a holistic health report.