[bug] github:yeet PR-body guidance is out of sync with standalone yeet

Open 💬 0 comments Opened Aug 11, 2026 by blib

What issue are you seeing?

Two official yeet skills currently define different pull-request authoring contracts:

  • GitHub plugin skill:

https://github.com/openai/plugins/blob/main/plugins/github/skills/yeet/SKILL.md

  • Standalone skill:

https://github.com/openai/skills/blob/main/skills/.curated/yeet/SKILL.md

The GitHub plugin version says that a PR body should cover “the checks used to validate it”, but it does not:

  • discover repository pull-request templates;
  • distinguish behavioral evidence from routine automation;
  • default to omitting a Verification section;
  • prevent linters, formatters, generic test runs, hooks, or CI status from being presented as behavioral verification.

The standalone skill was updated later with these rules. It discovers PR templates, explains why before what changed, limits the description to the net change, and only includes verification when there is meaningful behavioral evidence.

Because these are distributed as separate official artifacts, installing the GitHub plugin exposes github:yeet with the older PR-body contract, while the standalone $yeet contains the newer contract. The same publishing task can therefore produce materially different PR descriptions depending on which official skill is selected.

Timeline
  • 2026-01-27: the standalone yeet skill was added to openai/skills:

https://github.com/openai/skills/commit/aac2078f9f293e5335f5efe33148f40d75b56389

  • 2026-03-18: the GitHub plugin was added to openai/plugins with its own bundled yeet skill:

https://github.com/openai/plugins/commit/1540745b82d5d139be8912fc3db42dadf2da60a7

  • 2026-05-18: the standalone skill received template discovery and stricter PR-body and verification guidance:

https://github.com/openai/skills/commit/590b49edc158611a2b2ed715ae73f27eb70d251a

  • 2026-06-22: openai/skills was deprecated in favor of openai/plugins:

https://github.com/openai/skills/commit/778b0e6129cf18cbaee3bf11479f583fadae8d03

  • 2026-08-11: the current openai/plugins file still has no commits after its original 2026-03-18 addition and does not contain the 2026-05-18 standalone improvements.

The drift therefore existed before the old repository was deprecated and remained unresolved after openai/plugins became the designated destination.

What steps can reproduce the bug?

  1. Install or enable the official GitHub plugin so that github:yeet is available.
  2. Inspect its current PR-body instructions:

https://github.com/openai/plugins/blob/main/plugins/github/skills/yeet/SKILL.md

  1. Compare them with the standalone skill:

https://github.com/openai/skills/blob/main/skills/.curated/yeet/SKILL.md

  1. Consider a change for which the only available results are routine checks such as:
  • git diff --check;
  • a generic secrets scan;
  • a formatter, linter, or type-check run;

while the changed behavior itself has not been exercised.

  1. The plugin contract provides no instruction to keep those results out of behavioral verification. The standalone contract explicitly does.

This is a source-level contract mismatch rather than a transport difference between the GitHub connector and gh.

What is the expected behavior?

The GitHub plugin should retain its connector-first publishing workflow while adopting the provider-neutral PR-authoring rules from the newer standalone skill:

  • discover and preserve repository PR templates;
  • explain why before what changed;
  • describe only the net change;
  • default to omitting Verification;
  • include verification only for reproduced behavior, a before/after observation, a targeted behavioral test, or a focused manual scenario;
  • do not present routine automation as behavioral evidence;
  • when a repository template requires verification, provide meaningful evidence or explicitly state that it was not run.

Ideally, the two distributions should share a canonical provider-neutral PR-body contract or have a synchronization check that prevents them from drifting again.

Additional information

Environment inspected on 2026-08-11:

  • Codex CLI: 0.144.3
  • GitHub remote plugin: 0.1.8-2841cf9749ae

openai/plugins currently has public issues and pull requests disabled, so this is being reported in openai/codex, consistent with other GitHub plugin skill reports such as:

https://github.com/openai/codex/issues/35876

View original on GitHub ↗