SkillsAdd

smithery.ai

codex-patches

Use this when updating the codex submodule or when patch files in codex-patches/ need to be added, regenerated, or repaired.

First seen Apr 12, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

upstream-patches Similar name
pulumi/agent-skills

Create, amend, remove, and rebase patches for Terraform provider submodules using `./scripts/up…

1 installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,401 B
  • docs SUMMARY.md 145 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Codex Patch Workflow

Use this skill whenever you touch the codex submodule (codex/) or the patch series in codex-patches/.

Apply Patches After Submodule Update

  1. Update the codex submodule to the target commit:
cd codex
git checkout <commit>
cd ..
  1. Apply our patches:
scripts/apply_codex_patches.sh

If a patch fails, fix only that patch before moving on.

Repairing a Broken Patch

General approach:

  1. Rehydrate codex/ to clean upstream before re‑diffing:
git archive codex-upstream/main | tar -x -C codex
  1. Re‑apply the remaining patches that still work. Fix conflicts manually if needed.
  2. Regenerate the broken patch by diffing the upstream file(s) against our modified version.

Regenerating a Patch (stable diff style)

Prefer diffs against the upstream tree to reduce context drift. For the full example script, see references/regenpatchexample.md.

Patch Hygiene

  • Keep each patch focused on a single feature or concern.
  • Avoid bundling unrelated changes into the same patch.
  • Do not include upstream-only changes; patches should be fork-only deltas.

Quick Smoke Test

After applying patches, run:

turbo lint
turbo typecheck