packages/shared-skills/skills/lcx-report-bug/SKILL.md
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:
code-yeongyu/lazycodex for LazyCodex, lazycodex-ai, omo-codex, marketplace, bundled skill, hook, MCP, installer, or packaging bugs.openai/codex for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior.Use GPT-5.5 style: outcome first, concise, evidence-bound. Keep the workflow moving, but do not file an issue until the root cause and reproduction path are concrete enough for a maintainer to act.
Create or prepare a GitHub issue or PR that includes:
lazycodex-generated label and footer tag$omo:debugging for the investigation. If Codex exposes only unqualified skill names in the current session, invoke $debugging and state that it is the OMO debugging skill./tmp before deciding ownership:CODEX_SRC="/tmp/openai-codex-source"
if [ ! -d "$CODEX_SRC/.git" ]; then
gh repo clone openai/codex "$CODEX_SRC" -- --depth=1
else
git -C "$CODEX_SRC" fetch --depth=1 origin
fi
If gh is unavailable, use git clone --depth=1 https://github.com/openai/codex "$CODEX_SRC".
4. Follow the debugging skill far enough to gather runtime evidence:
/tmp/openai-codex-source before choosing the target repo. Cite exact files, commands, logs, or source paths that support the routing decision.code-yeongyu/lazycodex when the bug is in LazyCodex integration, distribution, bundled plugin code, skills, hooks, MCP wiring, installer behavior, aliases, marketplace sync, docs, or any behavior that disappears in clean upstream Codex.openai/codex when the bug reproduces in clean upstream Codex without LazyCodex, or the failing behavior comes from Codex CLI core, plugin API contracts, sandboxing, approvals, config loading, or built-in tool behavior.TARGET_REPO="code-yeongyu/lazycodex" # or openai/codex
gh issue list --repo "$TARGET_REPO" --search "<short error or symptom>" --state open
LABEL_ARGS=()
if gh label create lazycodex-generated --repo "$TARGET_REPO" --color "7C3AED" --description "Created by LazyCodex" --force; then
LABEL_ARGS=(--label lazycodex-generated)
else
echo "Label management unavailable for $TARGET_REPO; keeping the footer tag only."
fi
If the selected repo is openai/codex and label management is not available, still include the footer tag in the body and continue without claiming label creation succeeded.
10. If no matching issue exists, create the issue with gh and apply the lazycodex-generated label.
11. Create a PR only when the user asked for a PR, the fix is already implemented on a branch, or the smallest correct fix can be safely made in the selected repo. Apply the lazycodex-generated label to every PR created by this skill. Otherwise create an issue with fix guidance.
Every issue body, evidence comment, and PR body created by this skill must use the GitHub label lazycodex-generated when the artifact supports labels. It must also end with this footer. Do not put content after it.
---
This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated
Write the issue body in English and keep it direct:
## Summary
[One or two sentences describing the user-visible failure.]
## Environment
- LazyCodex version:
- Codex version:
- OS:
- Install method:
- Relevant config:
## Repository Decision
- Target repository:
- Why this belongs there:
- LazyCodex evidence:
- Upstream Codex source evidence from `/tmp/openai-codex-source`:
## Reproduction
1. [Exact command or UI action]
2. [Exact next step]
3. [Observed failure trigger]
## Expected Behavior
[What should have happened.]
## Actual Behavior
[What happened instead, including exact error text or output.]
## Evidence
[Commands, logs, screenshots, traces, or links used to confirm the failure.]
## Root Cause
[Confirmed cause. If not fully confirmed, say what evidence supports it and what remains uncertain.]
## Proposed Fix
[Concrete implementation or operational fix. Include likely files, components, or commands.]
## Verification Plan
- [Check that reproduces the original failure]
- [Check that proves the fix]
- [Regression check for adjacent LazyCodex/Codex plugin behavior]
---
This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated
Use this when a PR is the right artifact:
## Summary
[One or two sentences describing the fix and the user-visible failure it resolves.]
## Repository Decision
- Target repository:
- Why this belongs there:
- LazyCodex evidence:
- Upstream Codex source evidence from `/tmp/openai-codex-source`:
## Root Cause
[Confirmed cause. Cite runtime evidence and source paths.]
## Fix
[What changed and why.]
## Verification
- [Check that reproduced the original failure before the fix]
- [Check that passes after the fix]
- [Regression check for adjacent behavior]
---
This issue or PR was generated by LazyCodex.
Tag: lazycodex-generated
Prefer gh:
ISSUE_BODY="/tmp/lcx-report-bug-$(date +%Y%m%d-%H%M%S).md"
$EDITOR "$ISSUE_BODY"
gh issue create --repo "$TARGET_REPO" --title "<clear title>" "${LABEL_ARGS[@]}" --body-file "$ISSUE_BODY"
If $EDITOR is not usable, write the file with the available file-editing tool, then run the same gh issue create command.
For an existing issue:
COMMENT_BODY="/tmp/lcx-report-bug-comment-$(date +%Y%m%d-%H%M%S).md"
gh issue comment "<issue-number>" --repo "$TARGET_REPO" --body-file "$COMMENT_BODY"
if [ "${#LABEL_ARGS[@]}" -gt 0 ]; then
gh issue edit "<issue-number>" --repo "$TARGET_REPO" --add-label lazycodex-generated
fi
For a PR from a branch pushed to the selected repo or fork:
PR_BODY="/tmp/lcx-report-bug-pr-$(date +%Y%m%d-%H%M%S).md"
gh pr create --repo "$TARGET_REPO" --title "<clear title>" "${LABEL_ARGS[@]}" --body-file "$PR_BODY"
After creating or commenting, return the issue or PR URL and a short summary of the evidence used.
If gh is unavailable, unauthenticated, or blocked, use Browser Use against the real GitHub page:
https://github.com/code-yeongyu/lazycodex/issues/new or https://github.com/openai/codex/issues/new.If Browser Use is unavailable but a desktop browser is open and authenticated, use Computer Use:
https://github.com/code-yeongyu/lazycodex/issues/new or https://github.com/openai/codex/issues/new.Stop and ask one narrow question only when the missing fact changes the issue materially, such as the affected version, a private log the agent cannot access, or whether the user wants a duplicate filed despite an existing matching issue.
Do not file:
/tmp/openai-codex-source