Compare HEAD with the latest published npm versions and list all unpublished changes by release layer. Triggers: unpublished changes, changelog, what changed, whats new.
lcx-contribute-bug-fix
lcx-contribute-bug-fix is an open-source workflow skill for Codex, published by code-yeongyu. Its author describes it as: “Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix iss…”. The project has 67k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-contribute-bug-fix`.
Installation
Add lcx-contribute-bug-fix to your agent with:
git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-contribute-bug-fixAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
When to use it
Reach for lcx-contribute-bug-fix when you want workflow help from Codex without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Ships in code-yeongyu/oh-my-openagent, an established project with 67,325 GitHub stars
- Declares compatibility with Codex
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does lcx-contribute-bug-fix do?
- Contribute a verified bug fix for LazyCodex, lazycodex-ai, omo-codex, bundled Codex skills, or upstream Codex CLI bugs. Opens a fork PR only for upstream openai/codex; LazyCodex-owned defects become a verified-fix issue on code-yeongyu/lazycodex (never a PR — that repo is a generated distribution mirror). Use when the user asks to fix a bug, contribute a bug fix, contribute to fix bug, open a PR for a bug, or debug and PR a LazyCodex/Codex defect.
- How do I install lcx-contribute-bug-fix?
- Run git clone https://github.com/code-yeongyu/oh-my-openagent ~/.claude/skills/lcx-contribute-bug-fix in your agent, then reload your skills. Review the source at https://github.com/code-yeongyu/oh-my-openagent before installing.
- Is lcx-contribute-bug-fix free to use?
- lcx-contribute-bug-fix is publicly available on GitHub, but code-yeongyu has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
- Which agents does lcx-contribute-bug-fix work with?
- lcx-contribute-bug-fix declares compatibility with Codex. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.
- Where does lcx-contribute-bug-fix come from?
- lcx-contribute-bug-fix ships inside code-yeongyu/oh-my-openagent, a repository that contains 43 catalogued skills in total. The repository's 67,325 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Workflow →Easter egg command - about oh-my-opencode. Triggers: omomomo, about, easter egg.
Nuclear-grade 16-agent pre-publish release gate. Runs /get-unpublished-changes to detect all changes since last npm release, spawns up to 10 ultrabrain agents for deep per-change analysis, invokes /review-work (5 agents) for holistic review, and 1 oracle for overall release synthesis. Runs ONLY when the user explicitly asks for a pre-publish review — a plain publish/release request MUST NOT trigger this; /publish ships directly. Triggers: 'pre-publish review', 'review before publish', 'release review', 'pre-release review', 'ready to publish?', 'can I publish?', 'pre-publish', 'safe to publish', 'publishing review', 'pre-publish check'.
Publish oh-my-opencode to npm by triggering the GitHub Actions publish workflow and verifying its artifacts. Ship-only: never runs pre-publish-review or re-reviews merged code unless the user explicitly asks. Argument: <patch|minor|major>. Triggers: publish, release, deploy, npm publish.
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.