Exposed Bug Fix Workflow
JetBrains/Exposed
Takes a GitHub or YouTrack issue for the Exposed project through reproduction, a failing test, a fix, validation and a pull request.
Debugs a concrete LazyCodex or upstream Codex defect, builds the smallest verified fix in a fresh temporary workspace, and routes the deliverable to the right repository and format.
Install LazyCodex Bug Fix Contribution
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fix --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .claude/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .claude/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fixType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .agents/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .agents/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .cursor/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .cursor/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/code-yeongyu/oh-my-openagent.git --path packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .gemini/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .gemini/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fixInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .github/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .github/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-contribute-bug-fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/code-yeongyu/oh-my-openagent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix .opencode/skills/lcx-contribute-bug-fix && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "lcx-contribute-bug-fix" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix into .opencode/skills/lcx-contribute-bug-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-contribute-bug-fix", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
lcx-contribute-bug-fix- GitHub stars
- 70k
- Token cost
- ~2.8k tokens
- SKILL.md length
- 773 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 45
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Debugs a concrete LazyCodex or upstream Codex defect, builds the smallest verified fix in a fresh temporary workspace, and routes the deliverable to the right repository and format.
- Works in 4 steps: Read the user's bug report and identify… → Invoke $omo:debugging for the… → Materialize the latest sources under… → …
- Fixing a reported LazyCodex or bundled-skill bug with a verified patch
- SKILL.md covers Required Outcome, Required Workflow, Verified-Fix Issue Template… and PR Body Generator (openai/codex), plus 2 more sections
- Runs JavaScript scripts from its folder; calls git, gh and node; reaches github.com
What it does
Ownership decides the deliverable. For LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior or packaging, the target repository is a generated distribution mirror regenerated from source on every release, so the skill never opens a pull request there; instead it opens a verified-fix issue with the patch as a unified diff, reproduction logs, the root cause with source evidence, verification logs, a label and a footer tag. For upstream Codex CLI bugs that reproduce without LazyCodex, the deliverable is a pull request from a fork, built on a focused branch from a fresh clone, with the same logs, fix, label and tag, plus cleanup afterward.
The required workflow reads the bug report, invokes the project's own debugging skill for the investigation, then materializes the latest sources under a shared temporary source root, syncing both possible target checkouts on every run and comparing them before choosing where the fix belongs, validating any cached checkout before reuse so an incomplete git directory cannot route the fix to the wrong repository. A bundled script helps assemble the final PR body.
When your agent uses it
- Fixing a reported LazyCodex or bundled-skill bug with a verified patch
- Fixing an upstream Codex CLI bug that reproduces without LazyCodex
- Deciding whether a bug fix should become an issue or a pull request
- Producing reproduction and verification logs before and after a fix
Example prompts
- “Debug this LazyCodex installer bug and open a verified-fix issue with the patch.”
- “This looks like a Codex core bug, not a LazyCodex one. Fix it and open a fork PR.”
- “Reproduce this defect, fix it in a fresh clone, and give me the before and after logs.”
Requirements
- Git, to clone and work in a fresh temporary workspace
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Read the user's bug report and identify the affected surface.
- Invoke $omo:debugging for the investigation. If only unqualified skill names are exposed, invoke $debugging and state that it is the OMO…
- Materialize the latest sources under LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex-sources}", then decide the…
- Create a fresh temporary clone and branch under ${TMPDIR:-/tmp}. Do not modify the user's current repository for the target fix unless the…
What it can do on your machine
Read from SKILL.md and the folder at commit ab81169. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
gitghnode
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
LazyCodex Bug Fix Contribution loads about 2.8k tokens when it runs. Until then it costs about 119 tokens; SKILL.md has 773 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 773 words (~2,833 tokens).
“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.”
- name
- lcx-contribute-bug-fix
- metadata.short-description
- Contribute verified LazyCodex or Codex bug fixes
Files
SKILL.md and 2 other files (scripts) in packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix of code-yeongyu/oh-my-openagent.
- SKILL.md
- agents/openai.yaml
- scripts/create-pr-body.mjs
Open the folder on GitHubat commit ab81169
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders. This page covers the copy in code-yeongyu/oh-my-openagent, which our catalogue first saw on October 7, 2026.
Compare with similar skills
LazyCodex Bug Fix Contribution next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| LazyCodex Bug Fix Contribution this skillcode-yeongyu/oh-my-openagent | 70k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Pre-Release PR Triagejamiepine/voicebox | 57k | — | ~3.1k | Automated safety check: Pass | MIT | |
| Review Triage Phaseprisma/orm | 48k | — | ~995 | Automated safety check: Pass | Apache-2.0 | |
| PR Triagertk-ai/rtk | 83k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Adk Setupgoogle/adk-python | 22k | — | ~993 | Automated safety check: Notes | Apache-2.0 |
Similar skills
- Official
Pre-Release PR Triage
jamiepine/voicebox
Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.
- Official
Review Triage Phase
prisma/orm
Runs the triage step of the review-framework loop: reads fetched PR review state, builds `review-actions.json`, validates it and renders `review-actions.md`.
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
- Official
Adk Setup
google/adk-python
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…
Issue Tracer
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
More from code-yeongyu/oh-my-openagent
All 45 skills in this repoBrowser Control with Omowright
code-yeongyu/oh-my-openagent
Drives a real browser through the omowright library, either the user's own signed-in browser or a separate browser the code launches, for forms, QA, screenshots and scraping.
Codex Plugin QA
code-yeongyu/oh-my-openagent
Tests the omo Codex plugin in an isolated CODEX_HOME with a local mock model, proving hooks fired through app-server notifications without touching ~/.codex.
Coding Agent Session Finder
code-yeongyu/oh-my-openagent
Finds, reads and reconstructs past coding-agent sessions across Codex, Claude, OpenCode, Senpi and many other local agent logs.
ast-grep Structural Search
code-yeongyu/oh-my-openagent
Searches and rewrites code by syntax-tree shape across 25 languages with ast-grep, for codemods, structural queries and YAML lint rules, using a Python wrapper script.
LSP Setup
code-yeongyu/oh-my-openagent
Detects which languages a project uses, installs the matching language server, writes its config and checks it with a real call so diagnostics and go-to-definition work.
OpenCode QA Toolkit
code-yeongyu/oh-my-openagent
Tests the opencode coding agent itself: its CLI, server, plugin hooks and events, the terminal UI under tmux, and its SQLite session database, using tested helper scripts.
Related
Works with
Categories
Questions about LazyCodex Bug Fix Contribution
What does LazyCodex Bug Fix Contribution do?
Debugs a concrete LazyCodex or upstream Codex defect, builds the smallest verified fix in a fresh temporary workspace, and routes the deliverable to the right repository and format. Ownership decides the deliverable. For LazyCodex, lazycodex-ai, omo-codex, bundled skills, hooks, MCP wiring, installer behavior or packaging, the target repository is a generated distribution mirror regenerated from source on every release, so the skill never opens a pull request there; instead it opens a verified-fix issue with the patch as a unified diff, reproduction logs, the root cause with source evidence, verification logs, a label and a footer tag.
When should I use LazyCodex Bug Fix Contribution?
LazyCodex Bug Fix Contribution fits situations like: fixing a reported LazyCodex or bundled-skill bug with a verified patch; fixing an upstream Codex CLI bug that reproduces without LazyCodex; deciding whether a bug fix should become an issue or a pull request; producing reproduction and verification logs before and after a fix.
How do I install LazyCodex Bug Fix Contribution in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a claude-code`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix in code-yeongyu/oh-my-openagent) into .claude/skills/lcx-contribute-bug-fix in your project. Claude Code loads it when a task matches its description.
How do I install LazyCodex Bug Fix Contribution in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a codex`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-contribute-bug-fix in code-yeongyu/oh-my-openagent) into .agents/skills/lcx-contribute-bug-fix in your project. Codex loads it when a task matches its description.
Can I use LazyCodex Bug Fix Contribution in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-contribute-bug-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lcx-contribute-bug-fix, .gemini/skills/lcx-contribute-bug-fix, .github/skills/lcx-contribute-bug-fix and .opencode/skills/lcx-contribute-bug-fix in your project.
What does LazyCodex Bug Fix Contribution need to run?
Going by SKILL.md and its folder, LazyCodex Bug Fix Contribution needs JavaScript for the scripts in its folder and the command-line tools its instructions call (git, gh and node). Our summary lists: Git, to clone and work in a fresh temporary workspace.
Does LazyCodex Bug Fix Contribution access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is LazyCodex Bug Fix Contribution safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does LazyCodex Bug Fix Contribution use?
LazyCodex Bug Fix Contribution has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does LazyCodex Bug Fix Contribution use?
About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to LazyCodex Bug Fix Contribution?
Skills that share tags, products or a category with LazyCodex Bug Fix Contribution: Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars), Review Triage Phase (prisma/orm, 48k stars) and PR Triage (rtk-ai/rtk, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains LazyCodex Bug Fix Contribution?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,882 GitHub stars. The repository holds 45 skills in this directory. The repository was last updated on October 8, 2026.
Source: code-yeongyu/oh-my-openagent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.