flagrm 0.2.1 → 0.4.0

package/dist/core/verify/test-results.js

@@ -1,8 +1,9 @@
 /**
  * Read test counts and names from the result files a test command writes:
- * TRX (`dotnet test --logger trx`) and JUnit XML (Karma, Jest, Vitest, NUnit
- * and most CI reporters). Both are parsed with regexes over tags and
- * attributes, which is enough for these machine-written formats.
+ * TRX (`dotnet test --logger trx`), JUnit XML (Karma, Jest, Vitest, NUnit
+ * and most CI reporters) and Jest JSON (`jest --json`, Vitest's `json`
+ * reporter). They are parsed with regexes over tags and attributes, or
+ * JSON.parse, which is enough for these machine-written formats.
  */
 import fs from "node:fs";
 import path from "node:path";
@@ -142,13 +143,59 @@ export function parseJUnit(xml) {
     }
     return results;
 }
+/**
+ * Jest's `--json` output (Vitest's `json` reporter writes the same shape): a
+ * test is named by its `describe` titles and its own, joined like JUnit names;
+ * a test outside any `describe` by its file name. Undefined when the text isn't that.
+ */
+export function parseJestJson(text) {
+    let json;
+    try {
+        json = JSON.parse(text);
+    }
+    catch {
+        return undefined;
+    }
+    if (!Array.isArray(json?.testResults))
+        return undefined;
+    const results = empty();
+    for (const file of json.testResults) {
+        if (!file || typeof file !== "object" || !Array.isArray(file.assertionResults ?? []))
+            return undefined;
+        for (const test of file.assertionResults ?? []) {
+            if (!test || typeof test !== "object")
+                return undefined;
+            const owners = test.ancestorTitles?.length ? test.ancestorTitles : file.name ? [path.basename(file.name)] : [];
+            const status = test.status ?? "";
+            record(results, [...owners, test.title ?? ""].join(JUNIT_SEPARATOR), status === "passed" ? "passed" : status === "failed" ? "failed" : "skipped");
+        }
+    }
+    return results;
+}
+/**
+ * One result file by its content: TRX, Jest JSON or JUnit XML. Undefined when
+ * it can't be read as any, or the XML document isn't complete (still being written).
+ */
+function parseResultFile(text) {
+    if (/^\s*\{/.test(text))
+        return parseJestJson(text);
+    if (/<TestRun\b/.test(text))
+        return /<\/TestRun>\s*$/.test(text) ? parseTrx(text) : undefined;
+    return /<testsuites?\b/.test(text) && /(?:<\/testsuites?>|<testsuites?\b[^>]*\/>)\s*$/.test(text)
+        ? parseJUnit(text)
+        : undefined;
+}
+/** Whether results name every test that ran (read from result files), not only the failing ones a log names. */
+export function hasTestNames(results) {
+    return results !== undefined && results.source !== "log";
+}
 /**
  * Merge every result file matching `pattern` (an absolute path or glob)
  * modified at or after `since` — test runners keep older result files around.
  * Files in `claimed` that haven't changed since are skipped: another
  * project's run just wrote them, and an overlapping pattern
  * (`./**\/TestResults/*.trx`) would count them twice. The files read are
- * added to `claimed`. Undefined when no such file exists.
+ * added to `claimed`. Undefined when no such file exists or none can be read.
  */
 export function collectTestResults(pattern, since, claimed = new Map()) {
     // Filesystem timestamps can be coarser than Date.now().
@@ -164,8 +211,10 @@ export function collectTestResults(pattern, since, claimed = new Map()) {
         return undefined;
     const merged = empty();
     for (const { file } of files) {
-        const xml = fs.readFileSync(file, "utf8");
-        const parsed = /<TestRun\b/.test(xml) ? parseTrx(xml) : parseJUnit(xml);
+        // A file that is still being written, or isn't a result file, is skipped rather than failing the run.
+        const parsed = parseResultFile(fs.readFileSync(file, "utf8"));
+        if (!parsed)
+            continue;
         merged.total += parsed.total;
         merged.passed += parsed.passed;
         merged.failed += parsed.failed;
@@ -174,5 +223,5 @@ export function collectTestResults(pattern, since, claimed = new Map()) {
         merged.failedNames.push(...parsed.failedNames);
         merged.files.push(file);
     }
-    return merged;
+    return merged.files.length ? merged : undefined;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "flagrm",
-  "version": "0.2.1",
+  "version": "0.4.0",
   "description": "Guardrails for removing feature flags with AI coding agents (Claude Code, Copilot, Codex): skills, a baseline, a verify gate and a Stop hook.",
   "type": "module",
   "license": "Apache-2.0",
@@ -55,12 +55,14 @@
     "commander": "^13.1.0",
     "fast-glob": "^3.3.3",
     "picocolors": "^1.1.1",
+    "picomatch": "^4.0.7",
     "typescript": "^5.7.0",
     "yaml": "^2.7.0"
   },
   "devDependencies": {
     "@biomejs/biome": "2.5.10",
     "@types/node": "^22.13.0",
+    "@types/picomatch": "^4.0.3",
     "tsx": "^4.19.0",
     "vitest": "^3.0.0"
   }

package/skills/flagrm-remove/SKILL.md

@@ -16,9 +16,11 @@ You find and edit the code. `flagrm` records the state before you start and
 decides when you are done: **done means `flagrm verify <flag> --json` exited 0.**
 Run it as `npx --no-install flagrm`, one command per call, no `||` (plain `npx flagrm` is another package).
 
+Several flags (`/flagrm-remove A B C`): read [batch.md](batch.md) first; it runs this workflow once per flag.
+
 ## 1. Preconditions
 
-- `git status --porcelain` must print nothing. Otherwise ask the user to commit or stash.
+- `flagrm doctor` must not warn about uncommitted files (flagrm's own setup files and `exclude`d paths don't count). Otherwise ask the user to commit or stash.
 - No `flagrm.config.yaml`: run `flagrm init` and fill in project paths and build/test commands with the user.
   Its doctor reports a missing SDK, `cargo` or Docker: show it. For `cargo`/Docker, offer `flagrm scope`; `--write` only on a yes.
 - `flagrm list --json`: find the flag in `flags[]`. Not there: show the closest names and ask.
@@ -30,12 +32,12 @@ Run it as `npx --no-install flagrm`, one command per call, no `||` (plain `npx f
 
 `flagrm baseline <flag> --json` records the git commit, build and test results and the flag's `names[]`.
 A `checks[]` entry with a non-zero `exitCode` and a `failure`: a setup problem. Show the user `failure.message` (and `flagrm scope`); once fixed, rerun with `--force`.
-Without `failure`: a build, stop. Tests: stop if the failures (`results.failedTests`) could cover the flag's code; else ask the user to accept them as known.
+Without `failure`: a build, stop. Tests: stop if the failures (`results.failedTests`) could cover the flag's code; else ask the user to accept them as known, and on a yes run `flagrm baseline <flag> --accept failures`.
 
 ## 3. Find every usage
 
 - Grep for each name in `names[]`: code, templates, config and tests. `parameterizedTests[]` are test calls passing ON/OFF.
-- `suggestedNames[]`: values of the flag with generic names. Record each that carries only this flag, a local, parameter or field with `--file <its file>`.
+- `suggestedNames[]`: values of the flag with generic names. Record each that carries only this flag, a local, parameter or field with `--file <its file>` (repeat `--file` for each file; a component's template is added for you).
 - Follow the value further: a method or property returning it, a field or local holding it, a parameter
   it's passed as, a DI-registered bool. Record each so `verify` checks it, then grep for it:
   `flagrm baseline <flag> --name IsNewCheckoutEnabledAsync --kind wrapper` (`--kind alias` for a constant like `Flags.NewCheckout`).
@@ -67,22 +69,40 @@ Read `patterns.md` in this skill's directory when a case is unclear.
 | Check | Fix |
 |---|---|
 | `leftovers` | Remove each reference listed. A comment is a warning: reword or delete it. A test checking text you deleted tests the OFF path: delete it. ON text no test checks: say so in your report |
-| `dead-code` | Delete what the removal left unused |
+| `dead-code` | Delete what the removal left unused. A declaration "referenced only where it is declared" (warning): delete it if only the OFF path used it; else say why it stays |
 | `build` | Fix the error your edit caused; don't touch unrelated code. `tsc` skips templates: grep `.html` for each member you removed or renamed |
 | `tests` | A new failure means ON behavior changed: fix the edit, not the test. Known failures (failed at the baseline) only warn. A test listed as no longer running (`unexplained`) must be one you removed on purpose: say why. A changed test file whose tests didn't run: run them yourself and report it |
+| `lint` | Fix what your edit caused. An already-failing lint fails only on new error lines: fix those; other new lines it lists only warn |
+| `coverage` | Tell the user which changed files no command checks; don't add or change commands yourself |
+
+Exit 2 is a usage or config error: read the message. `--skip build,tests,lint,coverage` is fine for a quick check in between; only a full run counts, and the Stop hook won't let you finish on one with `--skip`. After three failed attempts on one check, show the user the findings. Don't run code generators or formatters after the passing verify; if you must, verify again.
+
+## 6. Hand back
+
+1. `flagrm verify <flag> --md` on the final tree (it reuses the passing build, test and lint runs; edit nothing after it): show its output exactly as printed; don't reword it or change its numbers. It must pass: the Stop hook checks it.
+2. **Notes**, 3–5 lines: what you kept on purpose, each remaining warning with its reason, follow-ups in the flag service. If `state` wasn't `on` and nobody confirmed ON, start with "Assumed ON everywhere".
+3. The commit message:
+
+<!-- commit-message:start -->
+**Proposed commit message**, in a code block:
+
+```
+chore: remove <flag> feature flag
 
-Exit 2 is a usage or config error: read the message. `--skip build,tests` is fine for a quick check
-in between; only a full run counts, and the Stop hook won't let you finish on one with `--skip`. After three failed attempts on one check, show the user the findings.
+<one or two sentences: which path stays and what was deleted>
+```
 
-## 6. Report
+- Follow the repository's convention instead when `git log --oneline -10` shows a different one.
+- A ticket in the branch name (`feature/feat-24586`): add it the way the log does (`#24586`, `FEAT-24586`), else `(#24586)` after the subject.
+- Wrap the body at 72 columns.
+<!-- commit-message:end -->
 
-In 3–5 lines: what was removed, what you kept on purpose, and each remaining warning with its
-reason. If `state` wasn't `on` and nobody confirmed ON, start with "Assumed ON everywhere".
-Suggest `/flagrm-verify <flag>` for the overview and commit message. Don't commit.
+Commit only when the user asked (in a batch: their answer at the start).
 
 ## Rules
 
 - Never lift code out of the OFF path into live code.
 - Match the file's formatting; don't refactor unrelated code.
 - Never edit `.flagrm/`. Rerun `flagrm baseline <flag>` only with `--name`, or with `--force` before your first edit (it refuses after).
-- Never `--skip` a failing check, and never change a test's expected value or the build/test commands to pass.
+- Never `--skip` a failing check, and never change a test's expected value or the build, test or lint commands or `covers` to pass. If the user changes the config mid-removal (say, to leave out tests that need services), run `flagrm baseline <flag> --accept config` once they confirm.
+- `baseline` and `verify` reuse a passing verify's build, test and lint results on the same tree and commands. If the user changed the machine (SDK, Docker, services) since, add `--no-reuse`.

package/skills/flagrm-remove/batch.md

@@ -0,0 +1,38 @@
+# Remove several flags
+
+Run SKILL.md's workflow once per flag, in the order given, one commit per flag.
+Each baseline reuses the previous flag's passing verify (seconds) only if the commit leaves the tree as verified.
+
+## Once, before the first flag
+
+1. SKILL.md step 1 preconditions. Find every flag in `flagrm list --json`; for one that's missing, show the closest names and ask.
+2. One table: flag, `state`, and for any not `on` the environments in `config[]` that change.
+   Ask once: "Remove all of these as ON everywhere?" On a no, drop the flags the user names.
+3. Ask once: "Commit each flag once its verify passes?"
+
+## Per flag
+
+Copy this checklist for each flag and tick it as you go:
+
+```
+<flag>:
+- [ ] baseline (step 2)
+- [ ] every usage found (step 3)
+- [ ] removed (step 4)
+- [ ] verify passes (step 5)
+- [ ] handed back (step 6)
+- [ ] committed
+```
+
+- The ON answer above is step 1's state answer: don't ask again.
+- Commit answer yes: commit with the proposed message, then start the next flag. No: show the message,
+  stop, and continue once the user says it's committed. The next baseline needs the previous removal committed.
+- A flag that needs the user (three failed attempts on one check, an unclear case) pauses the batch.
+  Never start a flag while the previous one is uncommitted.
+- Optional: if you can start subagents, run each flag in its own, one at a time. A subagent sees no
+  conversation history: give it the flag, that it is confirmed ON everywhere, the commit answer, and
+  "follow flagrm-remove's SKILL.md steps 2–6".
+
+## At the end
+
+One table: flag, commit, remaining warnings, kept on purpose.

package/skills/flagrm-verify/SKILL.md

@@ -35,14 +35,20 @@ Output, in this order:
    - follow-ups outside the repo: archive the flag in the flag service
      (LaunchDarkly, Azure App Configuration, ...), remove keys from deployment
      settings and secret stores.
-3. **Proposed commit message**, in a code block:
+3. The commit message:
 
-   ```
-   chore: remove <flag> feature flag
+<!-- commit-message:start -->
+**Proposed commit message**, in a code block:
 
-   <one or two sentences: which path stays and what was deleted>
-   ```
+```
+chore: remove <flag> feature flag
 
-   Follow the repository's convention instead when `git log --oneline -10` shows a different one.
+<one or two sentences: which path stays and what was deleted>
+```
+
+- Follow the repository's convention instead when `git log --oneline -10` shows a different one.
+- A ticket in the branch name (`feature/feat-24586`): add it the way the log does (`#24586`, `FEAT-24586`), else `(#24586)` after the subject.
+- Wrap the body at 72 columns.
+<!-- commit-message:end -->
 
 Never commit, push or open a PR unless asked. Write a PR description only on request, from the same output.