code-quality

Code Quality Review Review $ARGUMENTS (or the whole app if no argument is given) for code quality issues. Work through every step below in order and report all findings with file paths and line numbers. Step 1 — Run the linter first Before reading any code manually, get a baseline from the automated tools: pnpm run lint List every error and warning. Fix all errors before proceeding — lint errors are not negotiable. Warnings should be reviewed and resolved unless there is a documented exception. Also run the TypeScript compiler in strict mode to surface any hidden type issues: Show more Installs 1.1K Repository cognitedata/bui…r-skills GitHub Stars 4 First Seen May 7, 2026 Security Audits Gen Agent Trust Hub Pass Socket Pass Snyk Pass