codexplugin

Guide / best codex plugins github

Best Codex plugins & skills for GitHub

A shortlist for PR triage, CI failures, review comments, and shipping a draft PR — with copy-ready install commands.

00 — Intro

If you use OpenAI Codex on real repositories, GitHub is usually the first place to extend it. The official GitHub codex plugin covers pull requests, issues, and CI context. Pair it with a few focused skills and you can diagnose failing checks, address review threads, and open a draft PR without bouncing between the terminal and the GitHub UI.

This guide is a curated shortlist — not every GitHub-adjacent listing in the directory. Each pick includes when to install it, the exact command, and a verify prompt so you know the extension is live after restart.

01 — Shortlist

  1. 01
    GitHubPlugin

    Core connector for PRs, issues, CI, and publish flows

  2. 02

    Inspect failing GitHub Actions checks, summarize logs, then fix after approval

  3. 03
    YeetSkill

    Stage, commit, push, and open a draft PR in one gh CLI flow

  4. 04

    Find review threads on the current-branch PR and apply selected fixes

  5. 05

    Parallel multi-agent review for regressions, security, and performance

02 — Recommended order

  1. 01

    Install the official GitHub plugin first and complete OAuth if prompted.

  2. 02

    Restart Codex, then list open PRs to confirm the connector works.

  3. 03

    Add gh-fix-ci when Actions checks fail and you need log-backed diagnosis.

  4. 04

    Add yeet or gh-address-comments when you are ready to open or clean up a PR.

03 — Install & verify

Copy a command, run it, restart Codex, then try the verify prompt.

GitHubPlugincoding

Install this first. It is the official integration for repository work inside Codex and the foundation for the skills below.

$ npx codex-marketplace add openai/plugins/plugins/github --plugin

Verify

List my open pull requests and summarize what each one changes

Full detail page
Gh Fix CiSkillcoding

Use when a PR is red on GitHub Actions. It stays out of Buildkite and other external providers beyond reporting the details URL.

$ npx codex-marketplace add openai/skills/skills/.curated/gh-fix-ci --skill

Verify

Inspect failing PR checks on this branch and summarize the root cause

Full detail page
YeetSkillcoding

Use when the change is ready and you explicitly want Codex to ship a draft PR — not for casual local edits.

$ npx codex-marketplace add openai/skills/skills/.curated/yeet --skill

Verify

Yeet these changes as a draft PR with a clear title and why/what body

Full detail page

Use after reviewers leave comments. Have Codex list threads, then tell it which numbers to address.

$ npx codex-marketplace add openai/skills/skills/.curated/gh-address-comments --skill

Verify

List review comments on my open PR and summarize what each one asks for

Full detail page
Review SwarmSkillcoding

Optional depth when you want structured review angles before you merge — not a substitute for the GitHub plugin.

$ npx codex-marketplace add Dimillian/Skills/review-swarm --skill

Verify

Review this PR for regressions, security issues, and missing tests

Full detail page

04 — FAQ

Do I need both the GitHub plugin and gh-fix-ci?

Yes for CI debugging. The plugin brings repository context; gh-fix-ci drives the Actions log workflow with the gh CLI. Start with the plugin alone if you only need PR lists and summaries.

Is yeet safe to run on main?

Yeet creates a branch when you start from the default branch, then opens a draft PR. Still review the staged diff before you confirm, and do not use it when you only wanted a local commit.

Where is the step-by-step install checklist?

See the GitHub PRs use-case guide for a shorter install → verify path, then return here for the full shortlist.