typescript-audit
Skill13 starsChanged 7 months agoMITView on GitHub
Use when reviewing TypeScript code quality — run ESLint, check types, verify tests, flag common issues. Trigger on "audit", "typescript audit", "lint", "check TypeScript code".
In this repository19 other files it gives its agents.
- agent-auditSkill
- codebase-auditSkill
- commitSkill
- design-and-specSkill
- dispatching-parallel-agentsSkill
- doc-driftSkill
- execution-planningSkill
- explain-codeSkill
- post-implementationSkill
- pushSkill
- python-auditSkill
- receiving-code-reviewSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- terraform-auditSkill
- test-driven-developmentSkill
- trace-codeSkill
- verification-before-completionSkill
- writing-plansSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 29
After automated tools pass, check these (tools can't catch them):
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TypeScript Audit
Quick quality check for TypeScript projects. Run the automated tools, flag what they miss.
Steps
1. Run automated checks
# Lint
npx eslint .
# Type check
npx tsc --noEmit
# Tests
npx vitest runFix any failures before proceeding.
2. Manual review checklist
After automated tools pass, check these (tools can't catch them):
Types:
- No
anytypes — useunknown+ type guards - No type assertions (
as X) without justifying comment - Zod schemas match TypeScript interfaces (
z.infer<typeof Schema>) - No unparameterized generics
Error handling:
- No unhandled promise rejections — async handlers wrapped
- Express error middleware has 4 params (
err, req, res, next) - No silent
catch {}blocks — every handler logs or re-throws
Express patterns:
- Middleware mounted in correct order (parsers before routes, error handler last)
- Routes use proper HTTP methods and status codes
- Request bodies validated with Zod before use
next()called correctly in middleware chains
Code quality:
- No
console.login production code - No hardcoded ports, URLs, or credentials
- Functions under ~30 lines
- No deep nesting (>3 levels)
Security:
- No
eval()orFunction()on user input - CORS configured with explicit origins (no
*in production) - No secrets in code or config files
- Dependencies checked with
npm audit
3. Report
For each finding: file, line, what's wrong, suggested fix, priority (High/Medium/Low).
Group by: automated tool failures first, then manual findings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

