dev-diagnosis-cli 0.1.2 → 0.1.3

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Changelog
 
+## 0.1.3 — unreleased
+
+- Fix: nested build-output directories are reported by their full path
+  from the repo root (`packages/foo/dist/`) instead of a bare `dist/` —
+  the bare entry only matches top-level output, so `--fix` on a repo
+  whose build output lives in a subdirectory wrote an `.aiignore`
+  entry the next scan ignored, and the scan kept failing after the
+  fix. Files under one build directory are also rolled up into a
+  single row instead of one row per file. (53 tests.)
+
 ## 0.1.2 — 2026-11-11
 
 - New: `context --fix` (and `all --fix`) writes the `.aiignore`

package/README.md

@@ -92,7 +92,7 @@ The demo repo is intentionally noisy, so `all` exits 1: the context and flakes c
 
 ### `context` — what an AI agent should not read
 
-Walks the repo (skipping `.git`, `node_modules` and other hidden directories) and classifies every file: build output, large files over 1 MB, lockfiles, logs, binary payloads, secret-like files and environment templates. It prints a 0–100 score, the bytes lost per category, the noisy files, the files worth a look before sharing, and the `.aiignore` entries that would fix it. Files the repo's `.aiignore` already lists are excluded from the scan entirely — they are what the agent will not be handed, so they are not noise any more. `context --fix` writes the suggestions into `.aiignore` for you; `--json` includes the fix outcome in the output.
+Walks the repo (skipping `.git`, `node_modules` and other hidden directories) and classifies every file: build output, large files over 1 MB, lockfiles, logs, binary payloads, secret-like files and environment templates. It prints a 0–100 score, the bytes lost per category, the noisy files, the files worth a look before sharing, and the `.aiignore` entries that would fix it. Build-output directories are reported by their full path from the repo root (`packages/foo/dist/`, not a bare `dist/`) and rolled up into one row per directory, so the entry `--fix` writes matches nested build output too. Files the repo's `.aiignore` already lists are excluded from the scan entirely — they are what the agent will not be handed, so they are not noise any more. `context --fix` writes the suggestions into `.aiignore` for you; `--json` includes the fix outcome in the output.
 
 The score is the *noise-only* part of ai-context-doctor's score: 100 minus the category-weighted share of noise bytes (build 40, large 25, lockfile 20, log 15). The full ai-context-doctor score also weighs context volume, one file dominating, file sprawl and binary payloads, so its composite number reads lower on the same repo. The file classification itself is the same.
 
@@ -111,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 — 50 tests
+npm test            # node:test, no extra dependencies — 53 tests
 npm run example     # run the CLI against the demo fixture
 ```
 

package/lib/context.mjs

@@ -96,9 +96,15 @@ export function classifyPath(relativePath, size = 0) {
   const parts = normalized.split('/');
   const basename = parts[parts.length - 1];
 
-  for (const part of parts.slice(0, -1)) {
-    if (NOISE_DIRS.has(part)) {
-      return { noise: { label: `${part}/`, reason: NOISE_DIRS.get(part) }, suggestion: `${part}/` };
+  // A noise directory is reported by its full path from the repo root
+  // (packages/foo/dist/), not just its name: two build directories in
+  // different parts of the tree would otherwise print the same label,
+  // and the .aiignore entry --fix writes has to match the whole path —
+  // a bare dist/ only ignores top-level build output.
+  for (let i = 0; i < parts.length - 1; i += 1) {
+    if (NOISE_DIRS.has(parts[i])) {
+      const dir = `${parts.slice(0, i + 1).join('/')}/`;
+      return { noise: { label: dir, reason: NOISE_DIRS.get(parts[i]) }, suggestion: dir };
     }
   }
   if (LOCKFILES.has(basename)) {
@@ -239,12 +245,27 @@ export function scanDirectory(root, options = {}) {
   walk(absolute, absolute, files, state);
 
   const noise = [];
+  // One row per build-output directory, not one row per file inside it:
+  // a dist/ with hundreds of files would otherwise flood the noise list
+  // (and the score uses the summed bytes either way).
+  const dirNoise = new Map();
   const review = [];
   const suggestions = new Set();
   for (const file of files) {
     const result = classifyPath(file.relativePath, file.size);
     if (result.noise) {
-      noise.push({ ...result.noise, bytes: file.size, path: file.relativePath.split(path.sep).join('/') });
+      const item = { ...result.noise, bytes: file.size, path: file.relativePath.split(path.sep).join('/') };
+      if (item.label.endsWith('/')) {
+        const existing = dirNoise.get(item.label);
+        if (existing) existing.bytes += file.size;
+        else {
+          const aggregated = { label: item.label, reason: item.reason, bytes: file.size, path: item.label };
+          dirNoise.set(item.label, aggregated);
+          noise.push(aggregated);
+        }
+      } else {
+        noise.push(item);
+      }
       if (result.suggestion) suggestions.add(result.suggestion);
     } else if (result.review) {
       review.push({ ...result.review, bytes: file.size, path: file.relativePath.split(path.sep).join('/') });

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.2"}
+{"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.3"}