Triagebot Action Bug Triage
withastro/astro
Takes a bug report for the triagebot-action GitHub Action through reproduction, root-cause diagnosis, an intended-behavior check and a fix attempt.
Investigates a LazyCodex or Codex CLI defect, decides which GitHub repository owns it, and drafts an evidence-backed issue or pull request with repro steps.
Install LazyCodex Bug Reporter
$ npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-report-bug --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-report-bug .claude/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .claude/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bugType 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-report-bug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-report-bug --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-report-bug .agents/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .agents/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-report-bug --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-report-bug .cursor/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .cursor/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bug--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-report-bug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install code-yeongyu/oh-my-openagent lcx-report-bug --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-report-bug .gemini/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .gemini/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bugInstalls 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-report-bug -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-report-bug .github/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .github/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bug -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-report-bug --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-report-bug .opencode/skills/lcx-report-bug && 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-report-bug" agent skill from https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug into .opencode/skills/lcx-report-bug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "lcx-report-bug", 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-report-bug- GitHub stars
- 70k
- Token cost
- ~3k tokens
- SKILL.md length
- 996 words
- Files
- 2
- Skills in repo
- 44
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Investigates a LazyCodex or Codex CLI defect, decides which GitHub repository owns it, and drafts an evidence-backed issue or pull request with repro steps.
- Works in 9 steps: Read the user's bug report and identify… → Invoke $omo:debugging for the… → Materialize the latest LazyCodex and… → …
- Reporting a bug in LazyCodex, lazycodex-ai or the omo-codex plugin
- SKILL.md covers Goal, Required Workflow, Required Label And Footer and Issue Body Template, plus 5 more sections
- Calls git and gh; reaches github.com
What it does
Each bug is routed to the repository that owns it. Problems in LazyCodex itself, such as the installer, bundled skills, hooks, MCP servers, packaging or the marketplace, go to the code-yeongyu/lazycodex repo and are always filed as issues, never pull requests, because that repo is regenerated from source on every release. Defects in the upstream Codex CLI that reproduce without LazyCodex go to openai/codex, the only repo where this skill may open a pull request.
Before filing anything it runs an investigation through the OMO debugging skill: at least three hypotheses, the smallest reproduction that exercises the real surface, and confirmation of the root cause by observing the failing state. It pulls the latest sources into a scratch directory to check ownership and line references. The English report covers environment, reproduction steps, expected and actual behavior, root cause, a fix approach with the likely files, a verification plan and a lazycodex-generated label and footer tag.
When your agent uses it
- Reporting a bug in LazyCodex, lazycodex-ai or the omo-codex plugin
- Working out whether a defect belongs to LazyCodex or to upstream Codex CLI
- Filing an upstream Codex CLI bug with a source-backed root cause
- Turning a half-understood failure into a reproducible issue maintainers can act on
Example prompts
- “File a bug for the LazyCodex installer failing to link the lazycodex-ai command on my machine.”
- “A Codex hook stops firing after a plugin update. Work out who owns the bug and open an issue.”
- “Report this upstream Codex CLI crash with a reproduction and a suggested fix.”
Requirements
- GitHub access for opening issues or pull requests
- The OMO debugging skill
- Network access to fetch LazyCodex and Codex sources
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Read the user's bug report and identify the affected surface: LazyCodex installer, Codex plugin, skill, hook, MCP, CLI alias, GitHub…
- Invoke $omo:debugging for the investigation. If Codex exposes only unqualified skill names in the current session, invoke $debugging and…
- Materialize the latest LazyCodex and upstream Codex sources under LAZYCODEX_SOURCE_ROOT="${LAZYCODEX_SOURCE_ROOT:-${TMPDIR:-/tmp}/lazycodex…
- Follow the debugging skill far enough to gather runtime evidence
- Compare runtime evidence with both $LAZYCODEX_SOURCE_ROOT/lazycodex-source and $LAZYCODEX_SOURCE_ROOT/chatgpt-subscription-source before…
- Choose the target repo
- Search for an existing issue in the selected repo before creating a new one. Search the other repo too when the ownership boundary is close
- If a matching open issue exists, add a comment with the new evidence instead of creating a duplicate.
- Ensure the generated label exists in repositories you control
What it can do on your machine
Read from SKILL.md and the folder at commit cbd7dd2. 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
Shell commands in SKILL.md call:
gitgh
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 Reporter loads about 3k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 996 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); files beside SKILL.md 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 996 words (~3,025 tokens).
“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:”
- name
- lcx-report-bug
- metadata.short-description
- Route LazyCodex or Codex bugs with source evidence
Files
SKILL.md and 1 other file in packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug of code-yeongyu/oh-my-openagent.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit cbd7dd2
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 Reporter 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 Reporter this skillcode-yeongyu/oh-my-openagent | 70k | — | ~3k | Automated safety check: Pass | Custom licence | |
| Triagebot Action Bug Triagewithastro/astro | 63k | — | ~639 | Automated safety check: Pass | Custom licence | |
| Issue TracerZaxbyHub/opencode-swarm | 488 | — | ~4.4k | Automated safety check: Pass | MIT | |
| Triage Issuesoftspark/ai-toolkit | 179 | — | ~1.3k | Automated safety check: Notes | Apache-2.0 | |
| Exposed Bug Fix WorkflowJetBrains/Exposed | 9.3k | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| React Router Bug Fix Workflowremix-run/react-router | 57k | — | ~1.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
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.
Triage Issue
softspark/ai-toolkit
Bug triage: explores codebase for root cause, files GitHub issue with TDD fix plan.
- Official
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.
React Router Bug Fix Workflow
remix-run/react-router
Fixes a React Router bug reported in a GitHub issue end to end: fetching the issue, validating the reproduction, writing a failing test and implementing the fix on a new branch.
OpenROAD Bug Fixer
The-OpenROAD-Project/OpenROAD
Fixes an OpenROAD bug from a GitHub issue or error code: finds the root cause, implements the fix, adds a regression test and prepares a signed-off commit.
More from code-yeongyu/oh-my-openagent
All 44 skills in this repoast-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.
Browser 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.
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 Reporter
What does LazyCodex Bug Reporter do?
Investigates a LazyCodex or Codex CLI defect, decides which GitHub repository owns it, and drafts an evidence-backed issue or pull request with repro steps. Each bug is routed to the repository that owns it. Problems in LazyCodex itself, such as the installer, bundled skills, hooks, MCP servers, packaging or the marketplace, go to the code-yeongyu/lazycodex repo and are always filed as issues, never pull requests, because that repo is regenerated from source on every release.
When should I use LazyCodex Bug Reporter?
LazyCodex Bug Reporter fits situations like: reporting a bug in LazyCodex, lazycodex-ai or the omo-codex plugin; working out whether a defect belongs to LazyCodex or to upstream Codex CLI; filing an upstream Codex CLI bug with a source-backed root cause; turning a half-understood failure into a reproducible issue maintainers can act on.
How do I install LazyCodex Bug Reporter in Claude Code?
Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug -a claude-code`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug in code-yeongyu/oh-my-openagent) into .claude/skills/lcx-report-bug in your project. Claude Code loads it when a task matches its description.
How do I install LazyCodex Bug Reporter in Codex?
Run `npx skills add code-yeongyu/oh-my-openagent --skill lcx-report-bug -a codex`. Or copy the skill folder (packages/omo-codex/plugin/components/lcx/skills/lcx-report-bug in code-yeongyu/oh-my-openagent) into .agents/skills/lcx-report-bug in your project. Codex loads it when a task matches its description.
Can I use LazyCodex Bug Reporter 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-report-bug -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-report-bug, .gemini/skills/lcx-report-bug, .github/skills/lcx-report-bug and .opencode/skills/lcx-report-bug in your project.
What does LazyCodex Bug Reporter need to run?
Going by SKILL.md and its folder, LazyCodex Bug Reporter needs the command-line tools its instructions call (git and gh). Our summary lists: GitHub access for opening issues or pull requests; The OMO debugging skill; Network access to fetch LazyCodex and Codex sources.
Does LazyCodex Bug Reporter 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 Reporter 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. Review the folder before installing.
What licence does LazyCodex Bug Reporter use?
LazyCodex Bug Reporter 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 Reporter use?
About 3k tokens (SKILL.md is roughly 12k 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 Reporter?
Skills that share tags, products or a category with LazyCodex Bug Reporter: Triagebot Action Bug Triage (withastro/astro, 63k stars), Issue Tracer (ZaxbyHub/opencode-swarm, 488 stars), Triage Issue (softspark/ai-toolkit, 179 stars) and Exposed Bug Fix Workflow (JetBrains/Exposed, 9.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains LazyCodex Bug Reporter?
code-yeongyu (a GitHub user) maintains it in code-yeongyu/oh-my-openagent, which has 69,850 GitHub stars. The repository holds 44 skills in this directory. The repository was last updated on October 7, 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.