dev-diagnosis-cli 0.1.0 → 0.1.1

package/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.1.1 — 2026-11-11
+
+- Docs: README now has npm version, CI, license and Node badges, and the
+  example output is regenerated verbatim — its paths match the repo layout.
+- Fix: the demo build and the cache test fixture now simulate 400 ms of
+  work (was 150 ms), so the cache check's verdict stays decisive even on
+  loaded CI machines — 0.1.1's first CI run failed one job (macOS, Node 22)
+  because a 41 ms saving fell under the 50 ms "cache pays" threshold.
+- Fix: `all` on a repo with no build cache no longer ends in FAIL — a
+  build command with no cache directory to measure is listed as skipped,
+  with the `--cache-dir` hint, instead of a failed cache check. (41 tests.)
+
 ## 0.1.0 — 2026-11-10
 
 - First release: one CLI combining the four diagnostic checks.

package/README.md

@@ -1,5 +1,10 @@
 # dev-diagnosis
 
+[![npm version](https://img.shields.io/npm/v/dev-diagnosis-cli.svg)](https://www.npmjs.com/package/dev-diagnosis-cli)
+[![CI](https://github.com/WJDdidi-1/dev-doctor/actions/workflows/ci.yml/badge.svg)](https://github.com/WJDdidi-1/dev-doctor/actions/workflows/ci.yml)
+[![license](https://img.shields.io/github/license/WJDdidi-1/dev-doctor.svg)](https://github.com/WJDdidi-1/dev-doctor/blob/main/LICENSE)
+[![node](https://img.shields.io/node/v/dev-diagnosis-cli.svg)](https://www.npmjs.com/package/dev-diagnosis-cli)
+
 One command that diagnoses your repo, your commands, your cache and your tests. It runs four checks that used to be four separate tools — whether an AI coding agent would read files it should not (`context`), why a CLI command is missing (`path`), whether a build cache actually pays (`cache`), and which tests are flaky (`flakes`) — and prints one report with a verdict per check. It is offline, has no runtime dependencies (Node.js standard library only), and works on Linux, macOS and Windows.
 
 ## Install and run
@@ -25,7 +30,7 @@ dev-diagnosis flakes <junit-dir>                    # flaky tests from JUnit XML
 dev-diagnosis all [path] --command <name> --flakes <dir> -- <build-command...>
 ```
 
-`all` always runs `context` on `[path]` (default: the current directory) and runs `path`, `flakes` and `cache` when their input is given. Checks without their input are listed as skipped, with the command that would run them, instead of silently pretending they ran. `--json` gives machine-readable output for `context`, `path`, `flakes` and `all`.
+`all` always runs `context` on `[path]` (default: the current directory) and runs `path`, `flakes` and `cache` when their input is given. Checks without their input are listed as skipped, with the command that would run them, instead of silently pretending they ran. A build command on a repo with no cache directory to measure is also listed as skipped rather than failing: nothing to measure is not a problem. `--json` gives machine-readable output for `context`, `path`, `flakes` and `all`.
 
 Exit codes: `0` every check that ran passed; `1` a check found something to fix or could not run; `2` usage error.
 
@@ -35,10 +40,10 @@ The repo ships a small demo project in `examples/demo-repo` (a build output, a l
 
 ```
 $ dev-diagnosis all examples/demo-repo --command node --flakes examples/runs -- node build.mjs
-dev-diagnosis — /home/hatch/workspace/dev-diagnosis-build/dev-diagnosis/examples/demo-repo
+dev-diagnosis — /home/hatch/workspace/dev-doctor-build/dev-doctor/examples/demo-repo
 
 == context ==
-Repo: /home/hatch/workspace/dev-diagnosis-build/dev-diagnosis/examples/demo-repo
+Repo: /home/hatch/workspace/dev-doctor-build/dev-doctor/examples/demo-repo
 Files: 9  Size: 1.68 MB  Score: 75/100 — Some context noise found
   build output: 98 B (0%) — lost 0 of 40
   large files: 1.68 MB (99.9%) — lost 25 of 25
@@ -72,11 +77,11 @@ com.example.CheckoutTest::appliesCoupon             1/2     2      new  passed-o
 FAIL  1 flaky, 1 always-failing across 2 runs
 
 == cache ==
-Cache dir: /home/hatch/workspace/dev-diagnosis-build/dev-diagnosis/examples/demo-repo/.cache
+Cache dir: /home/hatch/workspace/dev-doctor-build/dev-doctor/examples/demo-repo/.cache
 Command: node build.mjs
-Cold: 234 ms  Warm: 80 ms  Saved: 154 ms (66%)
-Verdict: cache pays — warm run is 154 ms (66%) faster than cold
-PASS  cache pays: cold 234 ms, warm 80 ms (warm run is 154 ms (66%) faster than cold)
+Cold: 491 ms  Warm: 90 ms  Saved: 401 ms (82%)
+Verdict: cache pays — warm run is 401 ms (82%) faster than cold
+PASS  cache pays: cold 491 ms, warm 90 ms (warm run is 401 ms (82%) faster than cold)
 
 Overall: FAIL — see the checks above
 ```
@@ -106,7 +111,7 @@ Reads JUnit XML across CI runs — each subdirectory of `<junit-dir>` is one run
 ## Development
 
 ```sh
-npm test            # node:test, no extra dependencies — 40 tests
+npm test            # node:test, no extra dependencies — 41 tests
 npm run example     # run the CLI against the demo fixture
 ```
 

package/bin/dev-diagnosis.js

@@ -333,8 +333,14 @@ function main(argv) {
           cacheCheck = runCache({ buildCommand: args.buildCommand, cacheDir: args.cacheDir, cwd: root });
           checks.cache = cacheCheck;
         } catch (error) {
-          checks.cache = { result: null, passed: false, verdict: `could not run: ${error.message}`, error: error.message };
-          cacheCheck = checks.cache;
+          if (String(error.message).includes('no cache directory found')) {
+            // Nothing to measure is not a failure: report it as skipped so
+            // `all` on a repo without a build cache does not end in FAIL.
+            skipped.push('cache — no cache directory found in this project; pass --cache-dir <dir> to measure one');
+          } else {
+            checks.cache = { result: null, passed: false, verdict: `could not run: ${error.message}`, error: error.message };
+            cacheCheck = checks.cache;
+          }
         }
       } else {
         skipped.push('cache — add -- <build-command>, for example: dev-diagnosis all -- node build.mjs');

package/examples/demo-repo/build.mjs

@@ -1,6 +1,8 @@
 // Demo build: slow on a cold cache, fast on a warm one.
 // If .cache/out.txt exists the work is already done; otherwise this
-// script simulates 150 ms of real work and writes the cache file.
+// script simulates 400 ms of real work and writes the cache file.
+// 400 ms (not 150) so the cold-vs-warm gap dwarfs Node startup time
+// and stays decisive on loaded CI machines.
 import fs from 'node:fs';
 import path from 'node:path';
 
@@ -9,7 +11,7 @@ const out = path.join(cacheDir, 'out.txt');
 if (fs.existsSync(out)) {
   console.log('cache hit');
 } else {
-  const until = Date.now() + 150;
+  const until = Date.now() + 400;
   while (Date.now() < until) { /* simulate work the cache would skip */ }
   fs.mkdirSync(cacheDir, { recursive: true });
   fs.writeFileSync(out, 'built\n');

package/lib/context.mjs

@@ -137,7 +137,9 @@ function walk(root, dir, out, state) {
   entries.sort((a, b) => (a.name < b.name ? -1 : a.name > b.name ? 1 : 0));
   for (const entry of entries) {
     const full = path.join(dir, entry.name);
-    const rel = path.relative(root, full);
+    // Always report forward slashes, so output (and tests) are identical
+    // on Windows, macOS and Linux.
+    const rel = path.relative(root, full).split(path.sep).join('/');
     if (entry.isDirectory()) {
       if (IGNORED_DIRS.has(entry.name)) continue;
       walk(root, full, out, state);

package/package.json

@@ -1 +1 @@
-{"author":"WJDdidi-1","bin":{"dev-diagnosis":"bin/dev-diagnosis.js"},"bugs":{"url":"https://github.com/WJDdidi-1/dev-doctor/issues"},"description":"One offline CLI that diagnoses a repo the way four small tools do: context noise for AI agents, missing CLI commands, build-cache value, and flaky tests.","engines":{"node":">=18"},"files":["bin/","lib/","examples/","README.md","LICENSE","CHANGELOG.md"],"homepage":"https://github.com/WJDdidi-1/dev-doctor#readme","keywords":["cli","diagnostics","ai-coding","context","build-cache","flaky-tests","path","developer-tools","offline"],"license":"Apache-2.0","name":"dev-diagnosis-cli","repository":{"type":"git","url":"git+https://github.com/WJDdidi-1/dev-doctor.git"},"scripts":{"example":"node examples/demo.mjs","test":"node --test"},"type":"module","version":"0.1.0"}
+{"author":"WJDdidi-1","bin":{"dev-diagnosis":"bin/dev-diagnosis.js"},"bugs":{"url":"https://github.com/WJDdidi-1/dev-doctor/issues"},"description":"One offline CLI that diagnoses a repo the way four small tools do: context noise for AI agents, missing CLI commands, build-cache value, and flaky tests.","engines":{"node":">=18"},"files":["bin/","lib/","examples/","README.md","LICENSE","CHANGELOG.md"],"homepage":"https://github.com/WJDdidi-1/dev-doctor#readme","keywords":["cli","diagnostics","ai-coding","context","build-cache","flaky-tests","path","developer-tools","offline"],"license":"Apache-2.0","name":"dev-diagnosis-cli","repository":{"type":"git","url":"git+https://github.com/WJDdidi-1/dev-doctor.git"},"scripts":{"example":"node examples/demo.mjs","test":"node --test"},"type":"module","version":"0.1.1"}