yeet skill is over opinionated

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

• #14971

Powered by Codex Action

Is there a way to disable a skill from consideration; e.g. I already have my own coding-pr skill with my preferences set; and it still defaults to using github:yeet.

Is there a way to disable a skill from consideration; e.g. I already have my own coding-pr skill with my preferences set; and it still defaults to using github:yeet.

Add a note in your ~/.codex/AGENTS.md not to use it (ask codex to write a negation for you)

Codex generated this ~/.codex/AGENTS.md:

# GitHub Naming Overrides

These instructions override conflicting defaults in bundled skills such as `github:yeet`.

- When Codex creates a git branch for work that may be pushed to GitHub, do not prepend `codex/` to the branch name.
- Use a plain descriptive branch name instead, for example `fix-login-timeout`, not `codex/fix-login-timeout`.
- When Codex opens a pull request, do not prepend `[codex] ` to the PR title.
- Use a plain descriptive PR title that reflects the change itself.
- Treat these naming rules as higher priority than skill-level defaults when they conflict.

Yet I still don't think these should be added to PRs and branches as well. It's best to simply follow the Principle of Least Surprise and not add something that was not asked.

Try "Don't use the github:yeet skill".

The instructions you're overriding are in the skill's body. Codex will only load that if it's triggered to do so. The instructions you need to override are the triggering instructions.

The second order problem is that when you add a plugin, you don't get to choose which skills to enable. Disabling the yeet skill should probably be something that can be done against the /skills command similar to top level skills. The github plugin is mostly good (though it's slower than it should be in a few tasks as it prefers checking first rather than the more speedy path of using a fallback for failure).

In my case the rest of the instructions in the github:yeet skill are mostly OK for me and pretty sane (though I would also prefer to just use gh for everything, resorting to gh api when needed, simply because it's faster).

Yeah got it. I mostly use jj-vcs, so any instructions to do things with git specific ideas are often wrong.

This skill also overrides Codex' own settings where I turned off Draft PRs yet Codex keeps making them. This is all a bit messy, there are toggles in Codex settings, as well as prompt overrides for some parts of the Git flow, but then here you say to update the AGENTS.md file. The Codex app lets me edit the Yeet skill but that takes me into some cache directory that will probably be wiped.

This skill also overrides Codex' own settings where I turned off Draft PRs yet Codex keeps making them. This is all a bit messy, there are toggles in Codex settings, as well as prompt overrides for some parts of the Git flow, but then here you say to update the AGENTS.md file. The Codex app lets me edit the Yeet skill but that takes me into some cache directory that will probably be wiped.

Seconding this. Not having a way to configure it to create Ready For Review PRs instead of drafts is a huge painpoint. Unlike a normal skill, i can't easily edit this, and i don't want my agents to have a conflicting plugin, Agents.md instruction,or custom skill which all compete with yeet for precedence.

This skill gets in the way of everyday development. Why is it on by default? It makes for a terrible experience. It is totally ill designed.

this is one of the worst things in Codex... so stupid... also Codex should use gh