ReddRadar
Agent skill
devcheck
Lint, format, typecheck, and verify the project is clean. Use after making changes, before committing, or when the user asks to verify quality.
Install this agent skill to your Project
npx add-skill https://github.com/cyanheads/mcp-ts-core/tree/main/skills/devcheck
Metadata
Additional technical details for this skill
- type
- workflow
- author
- cyanheads
- version
- 1.3
- audience
- external
SKILL.md
What It Runs
bun run devcheck runs a broader check suite than just lint + types. By default it includes local hygiene checks, MCP definition linting, Biome, TypeScript, and slow dependency/security checks unless --fast is passed. Tests are opt-in via --test.
| Check | Tool | Notes |
|---|---|---|
| TODOs / FIXMEs | git grep |
Fails on tracked TODO/FIXME markers outside excluded files |
| Tracked secrets | git ls-files |
Flags tracked .env, keys, credentials, and similar sensitive files |
| MCP definitions | bun run scripts/lint-mcp.ts |
Validates tool/resource/prompt definitions against framework rules |
| Biome | biome check |
Unified lint + format — read-only by default |
| TypeScript | tsc --noEmit |
Full project type check |
| Unused dependencies | depcheck |
Runs by default; network-free but slower on large repos |
| Security audit | bun audit |
Runs by default unless --fast or --no-audit |
| Outdated dependencies | bun outdated |
Runs by default unless --fast or --no-deps |
| Tests | vitest run |
Off by default; enable with bun run devcheck --test |
To auto-fix lint/format issues, run bun run format.
Steps
- Run
bun run devcheck - Read the failing checks in the summary and per-check output
- Fix the reported issues
- Re-run
bun run devcheckuntil clean - If the change touches runtime behavior, also run
bun run devcheck --testorbun run test - Do not consider this skill complete until the required commands exit successfully with no errors
Common Issues
| Check | Error Type | Typical Fix |
|---|---|---|
| TODOs / FIXMEs | Tracked work markers | Resolve or remove the marker before committing |
| Tracked secrets | Sensitive files in git | Add to .gitignore and remove from the index |
| MCP definitions | Definition lint errors | Fix schema/name/annotation issues reported by lint-mcp |
| Biome | Lint/format errors | Run bun run format to auto-fix, or address the flagged rule manually |
| TypeScript | Type errors | Fix type mismatches, missing properties, incorrect generics |
| Security audit | Vulnerabilities in direct deps | Update or replace the affected dependency |
| Outdated deps | Stale package versions | Run bun update or allowlist intentionally pinned packages |
Checklist
-
bun run devcheckexits with no errors - Tests run when needed (
bun run devcheck --testorbun run test)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
cyanheads/mcp-ts-core
add-resource
Scaffold a new MCP resource definition. Use when the user asks to add a resource, expose data via URI, or create a readable endpoint.
cyanheads/mcp-ts-core
field-test
Exercise tools, resources, and prompts with real-world inputs to verify behavior end-to-end. Use after adding or modifying definitions, or when the user asks to test, try out, or verify their MCP surface. Calls each definition with realistic and adversarial inputs and produces a report of issues, pain points, and recommendations.
cyanheads/mcp-ts-core
release
Verify release readiness and publish. The git wrapup protocol handles version bumps, changelog, README, commits, and tagging during the coding session. This skill verifies nothing was missed, runs final checks, and presents the irreversible publish commands.
cyanheads/mcp-ts-core
add-export
Add a new subpath export to the @cyanheads/mcp-ts-core package. Use when creating a new public API surface that consumers import from a dedicated subpath (e.g., @cyanheads/mcp-ts-core/newutil).
cyanheads/mcp-ts-core
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for `@cyanheads/mcp-ts-core`. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.
cyanheads/mcp-ts-core
api-utils
API reference for all utilities exported from `@cyanheads/mcp-ts-core/utils`. Use when looking up utility method signatures, options, peer dependencies, or usage patterns.
Didn't find tool you were looking for?