vk-fix-types
Skill1 starsChanged 4 months agoApache-2.0View on GitHub
⚡ Fix type errors
In this repository77 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- archifySkill
- banner-designSkill
- brandSkill
- chrome-devtoolsSkill
- code-reviewSkill
- computer-useSkill
- context-engine-debuggingSkill
- context-engine-exploringSkill
- context-engine-guideSkill
- context-engine-syncSkill
- debuggingSkill
- designSkill
- design-systemSkill
- docs-seekerSkill
- docxSkill
- pdfSkill
- pptxSkill
- xlsxSkill
- kubernetesSkill
- planningSkill
- playwrightSkill
- repomixSkill
- researchSkill
- slidesSkill
- ui-ux-pro-maxSkill
- vk-askSkill
- vk-bootstrap-autoSkill
- vk-brainstormSkill
- vk-cloneSkill
- vk-contentSkill
- vk-cook-routerSkill
- vk-cookSkill
- vk-debugSkill
- vk-design-from-visualSkill
- vk-designSkill
- vk-docsSkill
- vk-docs-summarizeSkill
- vk-fix-fastSkill
- vk-fix-hardSkill
- vk-fixSkill
- vk-fix-sourceSkill
- vk-fix-uiSkill
- vk-git-cmSkill
- vk-git-cpSkill
- vk-git-mergeSkill
- vk-git-prSkill
- vk-git-tagSkill
- vk-goalSkill
- vk-helpSkill
- vk-hoh-devSkill
- vk-hoh-planSkill
- vk-hoh-qaSkill
- vk-hoh-runSkill
- vk-integrate-polarSkill
- vk-integrate-sepaySkill
- vk-journalSkill
- vk-learnSkill
- vk-plan-archiveSkill
- vk-plan-fastSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Serial: run bun run typecheck / tsc / npx tsc once.
- Very specific: line 31
Never use any just to pass the type check.
≈ “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
Fix Types
Workflow
- Serial: run
bun run typecheck/tsc/npx tsconce. Capture the full error list — this is the shared input everything else partitions from. - Serial — partition: group errors by file. Errors in shared type/interface
definition files (e.g.
types.ts, a module'sinterfaces.ts) are the OVERLAP case (workflows/parallel-execution.md§2) — fix these first, they're the dependency root for everything else. - Serial: fix the shared-type-def errors (wave 0). Re-run typecheck to confirm the shared contract is correct before fanning out.
- Parallel (wave 1, ≤3-4/batch, per
workflows/parallel-execution.md§1/§4): print the Parallel Execution Matrix (file/cluster → owns → depends on wave 0 → verify), then spawn onecook-worker(haiku or sonnet viamodelparam) per remaining file or zero-cross-reference cluster (tier by fix complexity — mechanical type-annotation fix → haiku; logic-affecting fix → sonnet). Each owns exactly its file(s); brief = that file's error list + acceptance criterion "typecheck clean for this file, noanyused to silence it." - Serial (wave 2): final typecheck. Zero errors → done. New errors from a fix → loop to step 4 for the affected file only (bounded: 3 cycles, then escalate per Verification Gate — do not loop indefinitely).
Rules
- Never use
anyjust to pass the type check. - Print the Parallel Execution Matrix before step 4's fan-out.
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.

