Codex plugin that runs @code-yeongyu/comment-checker after successful apply_patch tool calls.
| Case | Result |
|---|---|
apply_patch succeeds |
parses tool_input.command and checks added/updated files |
non-apply_patch edit tool succeeds |
ignored |
checker exits 2 |
returns Codex PostToolUse blocking feedback so the model fixes or explains the warning |
| checker binary missing | emits no hook output |
| checker exits unexpectedly | leaves hook output unchanged |
Deletes are ignored because they cannot introduce new comments.
The plugin ships:
.codex-plugin/plugin.jsonfor Codex plugin discovery.hooks/hooks.jsonfor thePostToolUsehook.skills/comment-checker/SKILL.mdwith usage guidance.
The hook command is:
node "$PLUGIN_ROOT/dist/cli.js" hook post-tool-useNo MCP server or comment_check tool is exposed.
npm install
npm test
npm run typecheck
npm run check
npm pack --dry-runSmoke-test the hook:
node dist/cli.js hook post-tool-use < test/fixtures/post-tool-use.jsonFrom the marketplace root containing this plugin:
codex plugin marketplace add /path/to/codex-plugins
node /path/to/codex-plugins/scripts/install-local.mjs /path/to/codex-pluginsIf your local Codex build exposes plugin install commands, you can install from the UI or CLI instead. For older local builds, the marketplace installer builds and copies the plugin into ~/.codex/plugins/cache/<marketplace>/codex-comment-checker/0.1.0, installs runtime dependencies there, and enables:
[plugins."codex-comment-checker@code-yeongyu-codex-plugins"]
enabled = truemainis protected by.github/branch-ruleset.json.- CI runs Node 20 and 22 on Ubuntu and macOS.
- Releases are GitHub Releases tagged as
v<semver>. - Publishing runs from the
publishworkflow after a GitHub Release is published.
This plugin runs locally. It sends hook input to the local comment-checker binary and does not call a network service by itself.
MIT.
- pi-comment-checker - source extension this Codex plugin ports.
- comment-checker - native checker binary.