agentleFS
rommelporrasrommelporras/kiro-config/skills/typescript-audit/SKILL.md

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".

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
  1. Distinctive:

    After automated tools pass, check these (tools can't catch them):

    line 29

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 run

Fix any failures before proceeding.

2. Manual review checklist

After automated tools pass, check these (tools can't catch them):

Types:

  • No any types — use unknown + 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.log in production code
  • No hardcoded ports, URLs, or credentials
  • Functions under ~30 lines
  • No deep nesting (>3 levels)

Security:

  • No eval() or Function() 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.