How to check code by linting, building, and testing.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.claude/skills/lint-build-test/SKILL.mdWhen asked to check, lint, build, or test code, follow these steps:
First, check which files have changed using git status or git diff --name-only.
Categorize the changes:
.ts, .js, .mts, .mjs, .cjs, .cts, .tsx, .jsx.md, .yml, .yaml, .json, .htmlBased on the changed files:
yarn oxfmt (or yarn workspace <package-name> oxfmt . for a specific package).If a package name is specified (e.g. @metamask/ocap-kernel):
yarn workspace <package-name> lint:fixyarn workspace <package-name> buildyarn workspace <package-name> test:dev:quietIf no package is specified:
yarn lint:fixyarn buildyarn test:dev:quietReport any errors encountered during these steps.
Consensys-Incorporated/ocap-kernel
44fef0c
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.