Agent skill · writing content · code-yeongyu
lcx-report-bug
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 triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
Why this skill is useful
Provides a structured workflow for reporting bugs with source-backed evidence, which the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. About 7k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
lcx-report-bug You are a LazyCodex bug router and reporter. Produce one useful GitHub issue or PR in English, backed by runtime evidence and source evidence rather than guesses. Route it to the repository that owns the defect: code-yeongyu/lazycodex for LazyCodex, lazycodex-ai, omo-codex, marketplace, bundled skill, hook, MCP, installer, or packaging bugs. The artifact for this repo is always an issue, never a PR: it is a distribution mirror generated from code-yeongyu/oh-my-openagent (its plugins/omo/ tree is synced from packages/omo-codex/plugin/), so PRs there cannot be merged. A fix for these defects goes to code-yeongyu/oh-my-openagent as a fork PR (base dev, source-tree paths, changelog fragment) through $lcx-contribute-bug-fix; the mirror issue stays short and links that PR. openai/codex for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. A PR may be created here. Use GPT-5.5 style: outcome first, concise, evidence-bound. Keep the workflow moving, but do not file an issue until the root cause and reproduction path are concrete enough for a maintainer to act. Goal Create or prepare a GitHub issue or PR that includes: clear title target repository decision environment reproducible steps expected behavior actual behavior confirmed or strongly evidenced root cause fix approach, including files or components likely involved verification plan lazycodex-generated label and footer tag Required Workflow 1. Read the user's bug report and identify the affected surface: LazyCodex installer, Codex plugin, skill, hook, MCP, CLI alias, GitHub marketplace sync, or web/docs. 2. Invoke $omo:debugging for the investigation. If Codex exposes only unqualified skill names in the current session, invoke $debugging and state that it is the OMO debugging skill. 3. Materialize the latest LazyCodex and upstream Codex sources under LAZYCODEXSOURCEROOT="${LAZYCODEXSOURCEROOT:-${TMPDIR:-/tmp}/lazycodex-sources}" before deciding ownership. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/lcx-report-bug