Agent skill

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.

YeonGyu-Kim69,732★ · +488/wk · 2 repos on radarProfile →
codexclaude-codecursorNOASSERTION
Install
npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: none
Path: packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 67,209 · +483 this week
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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, because its contents are regenerated from the source tree on every release, so PRs there cannot be merged. - `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. This is the only repo where this skill may create a PR. 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 - verificatio

What's inside
Steps it walks through
  1. Goal
  2. Required Workflow
  3. Required Label And Footer
  4. Issue Body Template
  5. PR Body Template
  6. GitHub Creation Path
  7. Browser use fallback
  8. Computer use fallback
  9. Stop Conditions
Ships with 1 file
  • agents/openai.yaml
Commands it runs
mkdir -p "$LAZYCODEX_SOURCE_ROOT"
git -C "$DEST" rev-parse --is-inside-work-tree >/dev/null 2>&1 &&
git -C "$DEST" config --get remote.origin.url >/dev/null 2>&1
if [ -e "$DEST" ] && ! valid_source_checkout "$DEST"; then
mv "$DEST" "$QUARANTINED"
echo "Moved corrupt source cache $DEST to $QUARANTINED" >&2
fi
recover_corrupt_source_checkout "$DEST"
if [ ! -d "$DEST" ]; then
gh repo clone "$REPO" "$DEST" -- --depth=1 \
More from oh-my-openagent
All skills →
About this skill
What does the lcx-report-bug skill do?

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.

How do I install it?

Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going