accelint-ts-audit-all

Coordinate multiple specialized skills to audit TypeScript files end-to-end.

17|1|Updated Mar 14, 2025
One-click install
npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill accelint-ts-audit-all-deckgl-fiber-renderer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-ts-audit-all
Source: https://github.com/deckgl-fiber-renderer/fiber.gl/tree/main/.agents/skills/accelint-ts-audit-all
Command: npx skills add https://github.com/deckgl-fiber-renderer/fiber.gl --skill accelint-ts-audit-all-deckgl-fiber-renderer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Orchestrates an end-to-end TypeScript audit workflow by coordinating multiple specialized skills to ensure thorough coverage, traceability, and safe changes.

Core Features & Use Cases

  • Multi-skill orchestration coordinates accelint-ts-testing, accelint-ts-best-practices, accelint-ts-performance, and accelint-ts-documentation for a unified audit process.
  • Interactive approvals enforce explicit user decisions for every change, maintaining code ownership and auditability.
  • Progress persistence saves audit state across sessions via audit-process and audit-history records, enabling resumption after context limits.
  • Isolated parallel audits use git worktrees to run audits in parallel without conflicts, enabling scalable audits of large codebases.

Quick Start

Invoke this skill with a file or directory path to start the 9-step TypeScript audit workflow.

Frequently Asked Questions about accelint-ts-audit-all

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

FAQPage Schema
How do I run an end-to-end TypeScript audit on a large codebase?

Run an end-to-end TypeScript audit by invoking the skill with a file or directory path to start a 9-step workflow. It coordinates specialized skills for testing, performance, and documentation while using isolated git worktrees to run parallel audits without conflicts.

Can I automate TypeScript file verification without losing code ownership?

Interactive approvals enforce explicit user decisions for every change during the TypeScript audit. This maintains code ownership and auditability while the automation coordinates multiple specialized skills to ensure thorough coverage and traceability.

How do isolated git worktrees help with parallel TypeScript audits?

Isolated git worktrees allow the TypeScript audit to run multiple specialized analyses in parallel without conflicts. This enables scalable audits of large codebases by preventing overlapping recommendations and conflicting changes across different audit scopes.

What is included in the 9-step TypeScript audit workflow?

The 9-step TypeScript audit workflow includes multi-skill orchestration coordinating testing, best practices, performance, and documentation checks. It applies to per-file or per-directory scopes and documents exact verification commands alongside progress tracking in audit files.

Does the TypeScript audit workflow support resuming after context limits?

TypeScript audit progress is saved across sessions via audit-process and audit-history files. This persistence enables you to resume the audit workflow after hitting context limits or interruptions, maintaining traceability of completed and pending file reviews.