typecheck
Skill2 starsChanged 4 months agoMITView on GitHub
Run the project's type checker (tsc, mypy, pyright, etc.) and fix the reported type errors at the source, without weakening types or suppressing. Use when the user says "run the type checker", "fix type errors", "make tsc pass", "fix the mypy errors", "typecheck this", or "why won't this compile".
2 other projects use a version of this.
Adopted by
Most recently taken up by
- Adelie-Squad/solosquadtheir own version, first seen Nov 4, 2026
- Stackbilt-dev/aegis-osstheir own version, first seen Oct 8, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- Adelie-Squad/solosquad★ 25same name
- Stackbilt-dev/aegis-oss★ 3same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository68 other files it gives its agents.
- a11ySkill
- api-docsSkill
- audit-logSkill
- benchmarkSkill
- bisectSkill
- cacheSkill
- changelogSkill
- cherry-pickSkill
- ci-setupSkill
- codeownersSkill
- commit-messageSkill
- connection-poolSkill
- contributingSkill
- coverageSkill
- db-migrateSkill
- dead-codeSkill
- debugSkill
- depsSkill
- diagramSkill
- dockerizeSkill
- docstringSkill
- e2eSkill
- env-exampleSkill
- error-handlingSkill
- explainSkill
- feature-flagSkill
- flaky-testSkill
- gitignoreSkill
- graceful-shutdownSkill
- graphqlSkill
- healthcheckSkill
- i18nSkill
- idempotencySkill
- licenseSkill
- lint-fixSkill
- loggingSkill
- migrateSkill
- mockSkill
- onboardSkill
- optimizeSkill
- paginationSkill
- pr-descriptionSkill
- pre-commitSkill
- profileSkill
- prune-branchesSkill
- rate-limitSkill
- readmeSkill
- rebaseSkill
- refactorSkill
- regexSkill
- releaseSkill
- resolve-conflictsSkill
- retrySkill
- review-diffSkill
- scaffoldSkill
- secrets-scanSkill
- security-headersSkill
- seedSkill
- soft-deleteSkill
- sqlSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Run the project's type checker and fix the errors it reports (scoped to $ARGUMENTS if given).
- Distinctive: line 26
If the checker isn't installed, report that and the install command instead of guessing errors.
- Very specific: line 29
A type error can be a real bug: When the checker is right that a value can be null, an access is unsafe, or a branch is unreachable, fix …
- Very specific: line 34
No silencing to force a pass: Don't use any/as any/@ts-ignore/# type: ignore/cast to make errors disappear.
- Distinctive: line 35
Don't loosen the project's config (strict flags, etc.) to reduce errors.
- Distinctive: line 37
Prefer precise fixes (real types, narrowing, generics) over broadening to a supertype that hides the problem.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Type checker config
!ls tsconfig.json jsconfig.json mypy.ini pyrightconfig.json pyproject.toml setup.cfg 2>/dev/null
!grep -hiE "strict|noImplicitAny|noUncheckedIndexedAccess|disallow_untyped|warn_return_any" tsconfig.json mypy.ini pyproject.toml 2>/dev/null | head -10
!cat package.json 2>/dev/null | grep -A30 '"scripts"' | grep -iE 'typecheck|tsc|type-check' | head
Instructions
Run the project's type checker and fix the errors it reports (scoped to $ARGUMENTS if given). Use the project's configured checker and strictness — don't impose your own.
Method
- Identify the checker and command from the config above, preferring an existing script:
- TS/JS:
tsc --noEmit(or thetypecheckscript); respect the existingtsconfigstrictness. - Python:
mypy <pkg>orpyright, per the project's config. - If the checker isn't installed, report that and the install command instead of guessing errors.
- TS/JS:
- Run it first to get the full, real error list and counts. Read the actual diagnostics — don't anticipate errors that aren't reported.
- Fix at the root, not the symptom. Group errors by underlying cause (one wrong type often cascades). For each: read the code and types to understand what's actually true, then correct the type or the code so it's sound — add a missing annotation, narrow a union, fix an incorrect signature, handle a
null/undefinedcase, import the right type. - A type error can be a real bug. When the checker is right that a value can be
null, an access is unsafe, or a branch is unreachable, fix the logic — don't just satisfy the checker. Flag these explicitly. - Re-run until clean (or until only genuinely-unfixable third-party cases remain), and show the before/after error counts.
Rules
- No silencing to force a pass. Don't use
any/as any/@ts-ignore/# type: ignore/castto make errors disappear. A suppression is a last resort only for a real tooling/library gap — narrowly scoped, with a comment explaining why, and called out in the summary. - Don't loosen the project's config (strict flags, etc.) to reduce errors. If a setting seems wrong, raise it with the user rather than editing it.
- Preserve runtime behavior unless a type error reveals a genuine bug — in which case fix the bug and say so. Don't change logic just to dodge a type.
- Prefer precise fixes (real types, narrowing, generics) over broadening to a supertype that hides the problem.
- Summarize: the checker run, errors fixed grouped by cause, any real bugs uncovered, the remaining count, and anything suppressed and why.
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.

