accelint-ts-audit-all

Audit TypeScript files for test coverage, code quality, performance, and documentation.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-ts-audit-all-ahnd6474
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accelint-ts-audit-all
Source: https://github.com/Ahnd6474/Jakal-flow/tree/main/.skill-staging/skills/accelint-ts-audit-all
Command: npx skills add https://github.com/Ahnd6474/Jakal-flow --skill accelint-ts-audit-all-ahnd6474

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Large TypeScript codebases often lack consistent test coverage, code quality, performance optimization, and up‑to‑date documentation, making maintenance risky and time‑consuming. This skill provides a systematic, interactive audit that guarantees each file passes a thorough 9‑step process before changes are merged.

Core Features & Use Cases

  • Coordinates four specialized sub‑skills (testing, best‑practices, performance, documentation) in a single workflow.
  • Tracks progress across sessions with timestamped audit‑process and audit‑history files, allowing audits to be paused and resumed.
  • Executes all changes inside an isolated Git worktree to prevent conflicts with ongoing development.
  • Enforces interactive approval for every recommendation using a two‑phase overview and detailed diff pattern.
  • Runs verification commands exactly as defined by the project (test, build, lint) after each modification step.
  • Ideal for teams that need reliable, repeatable code quality improvements across many TypeScript files or whole monorepo packages.

Quick Start

Run accelint-ts-audit-all with the target file or directory path to start a full audit.

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 audit TypeScript files for test coverage, code quality, and performance?

You can audit TypeScript files by running this skill on a target directory, which coordinates testing, best-practices, performance, and documentation sub-skills to enforce a 9-step verification process with interactive approval for each change.

Can I pause a TypeScript code audit and resume it later across sessions?

Yes, you can resume a TypeScript code audit across sessions because the skill tracks progress using timestamped audit-process and audit-history files, allowing you to pause and continue the 9-step verification workflow later.

Does the TypeScript audit process require a specific Node.js project setup?

Yes, the TypeScript audit process requires a Node.js project with predefined test, build, and lint commands, which the skill executes after each modification to verify that changes pass your project's standards.

How does the interactive code audit handle changes without conflicting with ongoing development?

The interactive code audit prevents conflicts with ongoing development by executing all modifications inside an isolated Git worktree, keeping your main branch unaffected until changes are approved and merged.

What is the best way to systematically improve documentation across a large TypeScript monorepo?

The best way to improve documentation across a TypeScript monorepo is using an interactive audit workflow that coordinates specialized sub-skills, enforcing documentation updates through a two-phase overview and detailed diff pattern with user approval.