Skip to content

v0.2.0 — MCP server, one-command setup, and a screencast

Choose a tag to compare

@WJDdidi-1 WJDdidi-1 released this 12 Nov 12:23
· 15 commits to main since this release
ced617d

What's new

  • dev-diagnosis --mcp — the four checks as an MCP server on stdio (pure Node.js standard library, no new dependencies): five tools (diagnose_context, diagnose_path, diagnose_cache, diagnose_flakes, diagnose_all), each returning the same JSON the CLI's --json produces. --sandbox <dir> restricts every path the tools touch to that directory.
  • dev-diagnosis --skill-generate — writes a Claude Agent Skills SKILL.md (project or --global) telling an agent to run dev-diagnosis all when it starts work in a repo, fix what FAILs, and re-run to confirm. Never overwrites an existing SKILL.md.
  • dev-diagnosis setup — wires the MCP server into Claude Code, Codex CLI, Cursor and VS Code in one command. Previews exactly what will be written first; merges into existing configs without touching other entries; --dry-run previews, --check reports.
  • GitHub Action — action.yml at the repo root runs dev-diagnosis all in one CI step and fails the job when a check fails.
  • context now reports token cost — ≈ 439k tokens (estimate) next to the noise list, and estimatedTokens in --json.
  • all ends with a one-line summary — passed/failed/skipped counts, context noise bytes, cache saving — in text and --json.
  • README screencast — a 22 s terminal recording (docs/demo.gif): all finds ≈439k tokens of noise, --fix writes one .aiignore entry, a re-run comes back 94/100 PASS. Every line is verbatim CLI output.

Fixes

  • context --fix / all --fix (and MCP tools with fix: true) used to report the pre-fix verdict — exit 1 and FAIL — even though the fix had landed and a re-run scores clean. They now re-scan after writing .aiignore and report the post-fix score, verdict and exit code. Other failures are still not masked: all --fix exits 1 when flakes, path or cache still fail.
  • context --fix no longer writes review suggestions (e.g. secret-like files) into .aiignore — a basename pattern like secret.js hid every same-named file in the repo while fixing nothing. Review suggestions are advisory only (reviewSuggestions in --json).
  • context no longer lists noise that costs no points and tells you to fix it — on a 100/100 repo it still printed a fix for the lockfile, contradicting its own PASS.
  • Test suite now runs serially (cache timing skewed under parallel runs) and no longer leaks ~100 MB of temp dirs per run.

Verified

124/124 tests, self-check 100/100, real MCP protocol check 25/25 (JSON-RPC 2.0, sandboxing, error handling), real setup + skill end-to-end 33/33. Cold npx start 0.77 s to the first conclusion. No new runtime dependencies; Node >= 18; fully offline.

Install: npx dev-diagnosis-cli or npm install -g dev-diagnosis-cli