lcx-report-bug

Route LazyCodex or Codex bugs to the correct repository with runtime evidence.

3.2k|198|Updated May 25, 2026

Search Tags:#automation #debugging #routing #github #evidence #bug

Ready to run

npx skills add https://github.com/code-yeongyu/lazycodex --skill lcx-report-bug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lcx-report-bug
Source: https://github.com/code-yeongyu/lazycodex/tree/main/plugins/omo/skills/lcx-report-bug
Command: npx skills add https://github.com/code-yeongyu/lazycodex --skill lcx-report-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers and operators automatically prepare high-signal bug reports or PRs for LazyCodex, lazycodex-ai, omo-codex, Codex plugins, or upstream Codex CLI, ensuring issues are actionable and well-evidenced.

Core Features & Use Cases

Detects the affected surface (LazyCodex integration vs upstream Codex) and determines the correct repository for reporting.
Collects runtime evidence by comparing the latest LazyCodex and Codex sources and correlating with user-reported symptoms.
Generates a complete issue/PR body including environment, reproduction steps, observed vs expected behavior, root cause analysis, proposed fixes, and a verification plan, all labeled for lazycodex-generated workflows.

Quick Start

Provide a clear bug description and request the agent to file an issue with reproduction steps and evidence.

Frequently Asked Questions about lcx-report-bug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I report a bug in LazyCodex or Codex with proper reproduction steps?▼

To report a bug, provide a clear description and the agent gathers runtime evidence, compares LazyCodex and Codex sources, and generates an issue body with reproduction steps, root cause, and a verification plan.

How does bug routing work for LazyCodex integration versus upstream Codex CLI?▼

Bug routing identifies the affected surface by comparing the latest LazyCodex and Codex sources with user-reported symptoms, then determines the correct repository for filing the issue or PR.

Can I automatically generate a GitHub pull request body for a Codex plugin bug?▼

Yes, you can generate a PR body that includes environment details, observed versus expected behavior, root cause analysis, proposed fixes, and a verification plan, all labeled for lazycodex-generated workflows.

What information do I need to provide to file an actionable Codex bug report?▼

You need to provide a clear bug description and request issue filing. The automation then collects runtime evidence and correlates symptoms with source code to produce a high-signal report.

Why should I use automated evidence gathering for LazyCodex bug reports?▼

Automated evidence gathering ensures issues are actionable by comparing latest sources, generating hypotheses, and producing a minimal reproducible path rather than relying on manual debugging.

Does this bug reporting workflow work for omo-codex and other Codex plugins?▼

Yes, the workflow supports preparing high-signal bug reports or PRs for LazyCodex, lazycodex-ai, omo-codex, Codex plugins, and upstream Codex CLI by determining the correct repository for each.