Agent skill · Code Review & Quality

lcx-contribute-bug-fix

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

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

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

Facts
Files in the skill folder: 3
SKILL.md size: 11 KB
Bundled scripts: yes
Path: packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/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-contribute-bug-fix Use this skill to debug a concrete LazyCodex or Codex defect, implement the smallest correct fix in a fresh temporary workspace, and deliver it. Work in English, keep the body short, and support every claim with runtime or source evidence. Route ownership the same way as `$lcx-report-bug`, but the deliverable differs by target: - `code-yeongyu/lazycodex` for LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior, marketplace sync, docs, or packaging. Deliverable: a verified-fix issue with the patch embedded. NEVER open a PR or push a branch against this repo — its contents are regenerated from the source tree on every release, so PRs there cannot be merged and will be closed. - `openai/codex` for upstream Codex CLI bugs that reproduce without LazyCodex or come from Codex core behavior. Deliverable: a PR from a fork. ## Required Outcome For `openai/codex`, create a fork PR that includes: - a focused branch from a fresh `${TMPDIR:-/tmp}` clone/worktree - reproduction logs from before the fix - the smallest implementation that fixes the defect - verification logs from after the fix - apply `lazycodex-generated` when label man

What's inside
Steps it walks through
  1. Required Outcome
  2. Required Workflow
  3. Verified-Fix Issue Template (code-yeongyu/lazycodex)
  4. PR Body Generator (openai/codex)
  5. PR Body Template (openai/codex)
  6. Stop Conditions
Ships with 2 files
  • agents/openai.yaml
  • scripts/create-pr-body.mjs
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-contribute-bug-fix skill do?

Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.

How do I install it?

Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix --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