LazyCodex Bug Reporter (lcx-report-bug)

Investigates LazyCodex/omo-codex/Codex CLI defects with runtime and source evidence, then files a high-signal GitHub issue or PR in the repo that owns the bug.

Dev & CodingIntermediate★ 67,531⑂ 5,507AI score 8/10Last updated: Aug 9, 2026

What it does

Identifies the failing surface: installer, Codex plugin, skill, hook, MCP wiring, CLI alias, marketplace sync, or docs.
Clones and validates fresh checkouts of code-yeongyu/lazycodex and openai/codex into a temp source root, then compares runtime evidence against both to route the bug to the owning repository.
Enforces a real debugging loop: at least three hypotheses, the smallest reproduction, observed failing state, and a minimal fix path.
Searches for duplicates first and comments new evidence on an existing issue instead of filing again.
Files the issue via gh using a strict template (Summary, Environment, Repository Decision, Reproduction, Evidence, Root Cause, Proposed Fix, Verification Plan) with the lazycodex-generated label and footer.
Falls back to Browser Use, then Computer Use, when gh is missing, unauthenticated, or blocked. PRs are allowed only against openai/codex.

Who it's for

Users of LazyCodex / lazycodex-ai / omo-codex who hit bugs and want them reported properly.
Developers who need to separate upstream Codex CLI defects from wrapper-layer defects.
Maintainers standardizing bug-report quality across a team.

Examples

"Hooks stopped loading after installing omo-codex" → source comparison shows a bundled-hook defect, so an issue is filed on code-yeongyu/lazycodex.
"Codex sandbox approval prompt loops forever" → reproduces on clean upstream Codex, so it goes to openai/codex, with a PR if a verified fix branch exists.
"Has anyone reported this error yet?" → gh issue list --search finds a match, and the skill posts an evidence comment instead of a duplicate.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/HEAD/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)

Download the ZIP with the button below.
In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.

↓ Download ZIP

Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/lcx-report-bug/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone --depth=1 https://github.com/code-yeongyu/oh-my-openagent.git /tmp/omo && mkdir -p ~/.claude/skills && cp -r /tmp/omo/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

Prerequisites: install git and the GitHub CLI (gh), then authenticate with gh auth login.
Clone the repository: git clone --depth=1 https://github.com/code-yeongyu/oh-my-openagent.git /tmp/omo
Copy the skill folder: mkdir -p ~/.claude/skills && cp -r /tmp/omo/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug ~/.claude/skills/
Verify that ~/.claude/skills/lcx-report-bug/SKILL.md exists.
Restart Claude Code and try a request like "report this LazyCodex bug for me".
(Optional) Change the source cache location by adding export LAZYCODEX_SOURCE_ROOT=~/.cache/lazycodex-sources to your shell profile.

View source on GitHub ↗License: NOASSERTION