lcx-contribute-bug-fix

Reproduce LazyCodex and Codex defects and generate minimal verified patches.

3.2k|198|Updated May 25, 2026

Search Tags:#automation #git #workflow #debugging #verification #patch #bug-fix

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Contribute and verify bug fixes for LazyCodex, lazycodex-ai, omo-codex, and upstream Codex CLI defects, delivering smallest patches and documented fixes to the appropriate repo.

Core Features & Use Cases

Reproduce defects in an isolated, fresh workspace with deterministic steps.
Generate the smallest correct patch and a verified-fix artifact (issue for LazyCodex or a fork PR for upstream Codex) for the target repository.
Provide auditable verification logs and patch diffs to accompany the deliverable.

Quick Start

Start a fresh debugging session and begin the end-to-end bug-fix workflow.

Frequently Asked Questions about lcx-contribute-bug-fix

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

FAQPage Schema

How do I create a verified bug fix patch for a Git repository?▼

To create a verified bug fix patch, you reproduce the defect in an isolated workspace, generate the smallest correct patch, and deliver a verified-fix issue or fork PR with auditable logs. This ensures the bug fix is traceable and verifiable.

What is the best way to reproduce a Git bug in an isolated workspace?▼

Reproducing a Git bug in an isolated workspace involves setting up a fresh temporary work tree with deterministic steps. This prevents local environment contamination and ensures the bug reproduction is reliable before generating a patch.

Do I need the gh CLI to submit a verified-fix issue or fork PR?▼

Yes, you need the gh CLI to submit a verified-fix issue or fork PR. Local Git and gh CLI access are required to interact with the target repositories and deliver the documented bug fix patches to the appropriate repo.

How does automated bug fix verification work for upstream Codex?▼

Automated bug fix verification works by reproducing the defect, generating the smallest correct patch, and providing auditable verification logs. It enforces isolated work trees and explicit tagging with a generated footer for upstream Codex repositories.

Can I use this workflow to fix defects across both LazyCodex and openai/codex?▼

Yes, you can use this workflow to fix defects across LazyCodex, lazycodex-ai, and openai/codex. It generates a verified-fix issue for LazyCodex or a fork PR for upstream Codex, covering patch generation and explicit tagging.