Skip to content

Releases: systemfsoftware/comment-checker

v0.3.6

Choose a tag to compare

@github-actions github-actions released this 01 Oct 19:33
d123fb1
  • The Nix flake build no longer writes to /homeless-shelter on machines where Nix runs without a sandbox (the macOS default), so rebuilding the flake or re-entering its direnv shell after an update no longer fails with "home directory /homeless-shelter exists".

v0.3.5

Choose a tag to compare

@github-actions github-actions released this 29 Sep 22:43
185b6fd
  • The documented Claude Code hook command no longer exits without reading the tool payload, so hosts that pipe large payloads no longer fail with a broken pipe. When comment-checker is not on PATH it now tries direnv exec next. When neither finds the checker, the hook reads the whole payload, prints comment-checker did not run — nothing checked this write. and exits 1. When the checker runs but exits with a code other than 0 or 2, for example after a crash, the hook reads the rest of the payload, prints comment-checker failed (exit <code>) — nothing checked this write. and exits 1. If you copied an earlier snippet, replace its command with the one in the README.
    • The Claude Code plugin hook no longer exits without reading the tool payload, so hosts that pipe large payloads no longer fail with a broken pipe. It passes through only the checker's own exit codes 0 and 2. When the checker cannot be found, or deno is missing or fails to start, the hook reads the whole payload, prints comment-checker did not run — nothing checked this write. and exits 1. When the checker runs but exits with any other code, the hook prints comment-checker failed (exit <code>) — nothing checked this write. and exits 1, where it used to pass that code through.

v0.3.4

Choose a tag to compare

@github-actions github-actions released this 30 Aug 23:13
4e899a2
  • The hook no longer crashes on startup in some environments and silently skips every write, and it no longer needs write access to your files — it flags unnecessary comments read-only and reports them to the model.

v0.3.3

Choose a tag to compare

@github-actions github-actions released this 30 Aug 06:07
a347d2f
  • Build the CLI binary directly from source in the Nix flake instead of fetching release assets, ensuring environments using Nix or direnv run the matching version with full command support.

v0.3.2

Choose a tag to compare

@github-actions github-actions released this 28 Aug 15:55
f81a2e3
  • The PostToolUse hook command now invokes deno run --config <plugin>/hooks/deno.jsonc … <plugin>/hooks/run.ts explicitly. The config file is what makes Deno treat the hook as a first-class module instead of node-compat material: without it, a hook living under node_modules (as an installed plugin does) cannot resolve @std/* or arktype and never reaches the checker. Passing the config restores the TypeScript source (run.ts) with its real imports, replacing the compiled run.js shipped in 0.3.1.

v0.3.1

Choose a tag to compare

@github-actions github-actions released this 28 Aug 03:48
6a40771
  • The PostToolUse hook is shipped as compiled run.js instead of run.ts, so it runs on Deno versions that refuse type-stripping inside node_modules. Type-checking is preserved through JSDoc annotations and checkJs in hooks/deno.jsonc.

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Aug 03:13
b92478f
  • This repository is also a Claude Code plugin. Enabling it runs a PostToolUse hook that tries comment-checker --strip, then direnv exec. If both miss and the project has flake.nix, the error tells you to run direnv allow or nix develop.
    • --strip deletes whole-line flagged comments from the file named in the hook payload. Without the flag, the hook still only reports. After a strip, the message names a code change to make — rename, extract, or tighten a type — instead of asking you to delete the comment.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 25 Aug 16:18
47baa6e
  • Flagged-comment reports now go to stderr instead of stdout, so the agent that made the edit actually receives them. A blocked verdict previously exited 2 with its report on stdout, which the hook contract discards, so the block arrived carrying no explanation of what was flagged. If you capture reports yourself, read stderr. Exit codes are unchanged: 0 when nothing is flagged, 2 when something is.

v0.1.8

Choose a tag to compare

@github-actions github-actions released this 25 Aug 14:24
0969fb5
  • The --version flag now reports the same version as the installed package. Previously it always reported 0.1.0 regardless of which release was installed.

v0.1.7

Choose a tag to compare

@github-actions github-actions released this 25 Aug 05:54
feb47e8
  • Fix GitHub releases to include platform binaries for every supported operating system and architecture.