accelint-ts-audit-all_skill

Overview

This skill provides a comprehensive, command-only TypeScript file audit system that orchestrates multiple specialized audit skills (testing, best-practices, performance, documentation) with interactive, approval-driven changes. It uses isolated git worktrees and persistent audit-process files to track progress across sessions and avoid conflicts. The workflow enforces strict verification, PBT stability checks, and step-by-step saving to prevent lost context.

How this skill works

Given a file or directory path, the skill builds a TODO list of TypeScript files and creates an isolated git worktree for the audit. It runs four audit skills in a prescribed 8-step sequence per file: testing, combined best-practices+performance, verification, and documentation, saving progress after every step. All suggested edits are shown with a severity table and before/after diffs, and user approval is required for each numbered change. Tracking files live outside the worktree so audit metadata is never committed.

When to use it

• You need a repeatable, auditable TypeScript code review that includes tests, performance, and docs.
• You want to run parallel audits without interfering with main branches or other audits.
• You must ensure property-based tests are stable before merging changes.
• You need session persistence to resume large audits across multiple runs.
• You require interactive, granular approval for every change to maintain code ownership.

Best practices

• Always validate the path and verification commands before initializing an audit.
• Create a timestamped isolated worktree; never run audits directly on main branches.
• Run accelint-ts-testing first and never skip test coverage verification.
• Run best-practices and performance analyses together and merge or present conflicts explicitly.
• Show the emoji severity table and full before/after diffs for all issues before asking for approval.
• Save detailed progress to the audit-process file after every completed step.

Example use cases

• Audit a single TypeScript file with tests, performance tweaks, and documentation updates in one session.
• Run a multi-file audit over several sessions while preserving partial results and resume points.
• Verify new property-based tests by running the test suite 100 consecutive times before accepting changes.
• Perform parallel audits on different worktrees to avoid merge conflicts on a shared repository.
• Enforce strict interactive approval flow for teams that require explicit consent for each automated change.