Skip to content
Skillpedia
General coding70k · #1715

lcx-contribute-bug-fix

Helps your agent contribute bug fixes for LazyCodex-related projects. It creates issues or pull requests to ensure code quality.

What it does

This tool helps fix errors in computer programs. It finds a specific problem, makes the smallest possible correction, and delivers that fix to be included in the project.

When to use it

  • ✓When a program doesn't work as expected.
  • ✓To fix a bug you have found.
  • ✓To contribute a solution to a known issue.

Example of what to ask your AI

“Fix the bug that causes the program to crash when I click the 'Save' button.”

Want more? Open the sections below.

How to use

The easiest way: copy the message below and paste it into Claude, ChatGPT, Cursor or any AI. It reads the skill and follows the instructions.

Skill link

https://github.com/code-yeongyu/oh-my-openagent/blob/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/SKILL.md

Ready-to-paste message

Use this skill to help me: https://github.com/code-yeongyu/oh-my-openagent/blob/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/SKILL.md Read the SKILL.md file at that link and follow its instructions for my task.
How it works

The tool first understands the problem and where it is in the code. Then, it creates a separate environment to test the fix without affecting current work. Finally, it applies the fix and verifies that the problem is resolved.

Installation

Easiest way: copy the skill link and paste it into Claude, ChatGPT or Cursor asking it to follow the instructions.

In the terminal (Claude Code, Codex, Cursor), in your project folder:

npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix

Or download just the file:

curl -L https://raw.githubusercontent.com/code-yeongyu/oh-my-openagent/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix/SKILL.md -o SKILL.md
Technical content (original SKILL.md)

Original text by the author, straight from GitHub.

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 management is available
  • the required LazyCodex footer tag Tag: lazycodex-generated
  • cleanup of temporary worktrees and clones

For code-yeongyu/lazycodex, create an issue (never a PR) that includes:

  • reproduction logs from before the fix
  • the root cause with source evidence
  • the verified patch as a unified diff, produced and tested in a fresh ${TMPDIR:-/tmp} clone/worktree
  • verification logs from after the fix
  • the lazycodex-generated label and the footer tag Tag: lazycodex-generated
  • cleanup of temporary worktrees and clones

Required Workflow

  1. Read the user's bug report and identify the affected surface. Before commands, apply the bundled ultrawork directive’s Task resources and todo rules; read those sections if absent from context.
  2. Invoke $omo:debugging for the investigation. If only unqualified skill names are exposed, invoke $debugging and state that it is the OMO debugging skill.
  3. Materialize the latest sources under 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:
# The default checkout cache is per-task under TMPDIR=$RUN_TMP.
LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}"
mkdir -p "$LAZYCODEX_SOURCE_ROOT"

valid_source_checkout() {
  DEST="$1"
  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
}

recover_corrupt_source_checkout() {
  DEST="$1"
  if [ -e "$DEST" ] && ! valid_source_checkout "$DEST"; then
    QUARANTINED="$DEST.corrupt.$(date +%Y%m%d%H%M%S)"
    mv "$DEST" "$QUARANTINED"
    echo "Moved corrupt source cache $DEST to $QUARANTINED" >&2
  fi
}

sync_latest_source() {
  REPO="$1"; DEST="$2"
  recover_corrupt_source_checkout "$DEST"
  if [ ! -d "$DEST" ]; then
    gh repo clone "$REPO" "$DEST" -- --depth=1 \
      || git clone --depth=1 "https://github.com/$REPO" "$DEST"
  fi
  if ! valid_source_checkout "$DEST"; then
    echo "Source cache $DEST is not a usable git checkout after clone" >&2
    return 1
  fi
  git -C "$DEST" remote set-url origin "https://github.com/$REPO.git" >/dev/null 2>&1 || true
  DEFAULT_BRANCH="$(git -C "$DEST" remote show origin | sed -n '/HEAD branch/s/.*: //p')"
  if [ -z "$DEFAULT_BRANCH" ]; then
    DEFAULT_BRANCH="$(git -C "$DEST" symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's#^origin/##')"
  fi
  if [ -z "$DEFAULT_BRANCH" ]; then
    echo "Could not determine default branch for $REPO in $DEST" >&2
    return 1
  fi
  git -C "$DEST" fetch --depth=1 origin "$DEFAULT_BRANCH"
  git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
}
sync_latest_source code-yeongyu/lazycodex "$LAZYCODEX_SOURCE_ROOT/lazycodex-source"
sync_latest_source openai/codex "$LAZYCODEX_SOURCE_ROOT/chatgpt-subscription-source"

…

FAQ

What is a 'fork PR'?

It's a request to add your changes to a project, created from a copy (fork) of the original project. It's common for contributing to open-source projects.

Why not send a 'PR' to the 'code-yeongyu/lazycodex' repository?

Because that repository is just an automatically generated copy. Fixes should be submitted as 'issues' (bug reports) with the solution included, not as a direct change request.

What does 'smallest possible fix' mean?

It means the tool only changes the code strictly necessary to solve the problem, without making larger or unnecessary modifications.

Details

Original description by the author

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 f

repo: code-yeongyu/oh-my-openagent

Popularity

GitHub stars
70k
Ranking position
#1715
License
NOASSERTION
Updated
10/16/2026

Is this skill useful?

0

Sign in to vote.

Comments

  • …

More skills from this repository

Similar skills