lcx-report-bug

name	lcx-report-bug
description	Create a high-signal bug issue or PR in the repo that owns the defect. Use this whenever the user asks to report, file, open, or triage a LazyCodex, lazycodex-ai, omo-codex, Codex plugin, or upstream Codex CLI bug, especially when they need source-backed root cause, reproduction steps, fix guidance, and GitHub routing.
metadata	{"short-description":"Route LazyCodex or Codex bugs with source evidence"}

lcx-report-bug

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. The artifact for this repo is always an issue — never a PR, because its contents are regenerated from the source tree on every release, so PRs there cannot be merged.
• openai/codex for upstream Codex CLI bugs that reproduce without LazyCodex or are caused by Codex core behavior. This is the only repo where this skill may create a PR.

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.

Goal

Create or prepare a GitHub issue or PR that includes:

• clear title
• target repository decision
• environment
• reproducible steps
• expected behavior
• actual behavior
• confirmed or strongly evidenced root cause
• fix approach, including files or components likely involved
• verification plan
• lazycodex-generated label and footer tag

Required Workflow

1. Read the user's bug report and identify the affected surface: LazyCodex installer, Codex plugin, skill, hook, MCP, CLI alias, GitHub marketplace sync, or web/docs.
2. Invoke $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.
3. Materialize the latest LazyCodex and upstream Codex sources under /tmp before deciding ownership. Re-sync on every run so a cached checkout cannot go stale — stale source produces wrong routing and dead line references:

sync_latest_source() {
  REPO="$1"; DEST="$2"
  if [ ! -d "$DEST/.git" ]; then
    gh repo clone "$REPO" "$DEST" -- --depth=1 \
      || git clone --depth=1 "https://github.com/$REPO" "$DEST"
  fi
  DEFAULT_BRANCH="$(git -C "$DEST" remote show origin | sed -n '/HEAD branch/s/.*: //p')"
  git -C "$DEST" fetch --depth=1 origin "$DEFAULT_BRANCH"
  git -C "$DEST" checkout -B "$DEFAULT_BRANCH" FETCH_HEAD
}
sync_latest_source code-yeongyu/lazycodex /tmp/lazycodex-source
sync_latest_source openai/codex /tmp/openai-codex-source

4. Follow the debugging skill far enough to gather runtime evidence:
   • form at least three plausible hypotheses
   • run the smallest reproduction that exercises the real surface
   • confirm the root cause by observing the failing state
   • identify the minimal fix path or maintainer action
5. Compare runtime evidence with both /tmp/lazycodex-source and /tmp/openai-codex-source before choosing the target repo. Cite exact files, commands, logs, or source paths that support the routing decision.
6. Choose the target repo:
   • Use 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.
   • Use 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.
   • If ownership remains ambiguous after evidence gathering, do not guess. Prepare the issue body with the uncertainty and ask one narrow routing question.
7. 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:

TARGET_REPO="code-yeongyu/lazycodex" # or openai/codex
gh issue list --repo "$TARGET_REPO" --search "<short error or symptom>" --state open

8. If a matching open issue exists, add a comment with the new evidence instead of creating a duplicate.
9. Ensure the generated label exists in repositories you control:

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 target repo is openai/codex AND the user asked for a PR, the fix is already implemented on a branch, or the smallest correct fix can be safely made there. Never create a PR or push a branch against code-yeongyu/lazycodex — always file an issue there, embedding the verified patch in the Proposed Fix section when one exists. Apply the lazycodex-generated label to every PR created by this skill. Otherwise create an issue with fix guidance.

Required Label And Footer

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

Issue Body Template

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 (runtime + `/tmp/lazycodex-source`):
- 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

PR Body Template

Use this only when a PR is the right artifact, which is only ever for openai/codex:

## 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 (runtime + `/tmp/lazycodex-source`):
- 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

GitHub Creation Path

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 a fork — openai/codex only, never code-yeongyu/lazycodex:

PR_BODY="/tmp/lcx-report-bug-pr-$(date +%Y%m%d-%H%M%S).md"
gh pr create --repo openai/codex --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.

Browser use fallback

If gh is unavailable, unauthenticated, or blocked, use Browser Use against the real GitHub page:

1. Open the new issue page for the selected repo: https://github.com/code-yeongyu/lazycodex/issues/new or https://github.com/openai/codex/issues/new.
2. Fill the title and body from the template.
3. Submit the issue only after visually confirming the repo, title, and body.
4. Capture the resulting issue URL.

Computer use fallback

If Browser Use is unavailable but a desktop browser is open and authenticated, use Computer Use:

1. Navigate to the new issue page for the selected repo: https://github.com/code-yeongyu/lazycodex/issues/new or https://github.com/openai/codex/issues/new.
2. Fill the title and body.
3. Verify the target repository and final text before submission.
4. Submit and capture the issue URL.

Stop Conditions

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:

• a PR or pushed branch targeting code-yeongyu/lazycodex — file the issue instead, always
• a vague issue without reproduction steps
• an issue that claims a root cause not supported by runtime evidence
• a duplicate when commenting on an existing issue is enough
• an issue without checking the latest /tmp/lazycodex-source and /tmp/openai-codex-source checkouts
• a LazyCodex issue when the bug is proven to reproduce in clean upstream Codex
• a fix PR without a concrete branch, implemented fix, and verification result