packages/omo-codex/plugin/components/comment-checker/README.md
Codex plugin that runs @code-yeongyu/comment-checker after successful edit-like PostToolUse hook calls.
| Case | Result |
|---|---|
apply_patch succeeds | parses tool_input.command and checks added/updated files |
write, edit, multi_edit, or multiedit succeeds | maps the Codex payload to the native checker hook input |
| non-edit tool succeeds | ignored |
checker exits 2 | returns Codex PostToolUse blocking feedback so the model fixes or explains the warning |
| checker binary missing or unavailable on the current platform | 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.json for Codex plugin discovery.hooks/hooks.json for the PostToolUse hook.skills/comment-checker/SKILL.md with usage guidance.The hook command is:
node "${PLUGIN_ROOT}/dist/cli.js" hook post-tool-use
No MCP server or comment_check tool is exposed.
npm install
npm test
npm run typecheck
npm run check
npm pack --dry-run
Smoke-test the hook:
node dist/cli.js hook post-tool-use < test/fixtures/post-tool-use.json
bunx lazycodex install
The installer builds and copies the plugin into ~/.codex/plugins/cache/sisyphuslabs/omo/0.1.0, registers the sisyphuslabs marketplace from the lazycodex Git repository, installs runtime dependencies there, and enables:
[features]
plugins = true
plugin_hooks = true
[plugins."omo@sisyphuslabs"]
enabled = true
main is protected by .github/branch-ruleset.json.v<semver>.publish workflow after a GitHub Release is published.This plugin runs locally. It sends hook input to the optional local comment-checker binary when available and does not call a network service by itself.
MIT.