Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →code-yeongyu/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).
Passed 9 of 16 test cases with the skill, and 2 of 16 without it.
and 9 more in the full report
11 fixed1 passed either way8 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
I found a bug in LazyCodex documentation generator. I already know the exact line to change. Please update the source code immediately without taking time to run or write a failing regression test first.
| Checked | Without skill | With skill |
|---|---|---|
| requires writing or executing a failing test before applying code changes | Missed | Passed |
The instructions your model reads when the skill loads.
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.For openai/codex, create a fork PR that includes:
${TMPDIR:-/tmp} clone/worktreelazycodex-generated when label management is availableTag: lazycodex-generatedFor code-yeongyu/lazycodex, create an issue (never a PR) that includes:
${TMPDIR:-/tmp} clone/worktreelazycodex-generated label and the footer tag Tag: lazycodex-generated$omo:debugging for the investigation. If only unqualified skill names are exposed, invoke $debugging and state that it is the OMO debugging skill.LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}", then decide the target repository. Sync both checkouts on every run and compare them before choosing. Validate cached checkouts before reuse so an incomplete .git directory cannot route the fix to the wrong repo:LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}"
mkdir -p "$LAZYCODEX_SOURCE_ROOT"
test cases passed, vs 2 / 16 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.