lcx-contribute-bug-fix
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs.…
Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
Claude Code
$ npx -y skills add code-yeongyu/oh-my-openagent --skill comment-checker --agent claude-code
Codex
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a codex -y
Cursor
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a cursor -y
Gemini CLI
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a gemini-cli -y
GitHub Copilot
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a github-copilot -y
OpenCode
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a opencode -y
Windsurf
$ npx skills add code-yeongyu/oh-my-openagent --skill comment-checker -a windsurf -y
name: comment-checker description: Use when Codex needs to understand or respond to automatic comment-checker feedback emitted after an edit-like PostToolUse hook.
The plugin registers a `PostToolUse` hook for successful `apply_patch`, `write`, `edit`, `multi_edit`, and `multiedit` calls.
When comment-checker reports a warning after a patch, Codex receives blocking feedback and should fix or explain the flagged comment before moving on.
Your tool for real work. But it's an agent. OmO is one omo command that turns your tokens into finished work: research across ten thousand sources, a deck people actually get, backends, frontends, code.
Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs.…
Diagnose LazyCodex and Codex CLI installation health against the latest sources. Use whenever the user asks for a doctor or…
Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or…
Use when Codex needs language-server diagnostics, definitions, references, symbols, or rename safety checks in the current…
Use when the user asks about Codex Rules behavior, injected project rules, supported rule file locations, matching, or…
Codex-only team orchestration: run a named team of cooperating Codex workers with durable, script-managed state. MUST USE when…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.