Feat: add Codex Plannotator skills#644
Merged
backnotprop merged 1 commit intobacknotprop:mainfrom May 2, 2026
Merged
Conversation
Owner
|
@leoreisdias thanks!! |
Owner
|
How will these get installed. Maybe we should ship a plugin |
Contributor
Author
thanks for the follow up @backnotprop ! about the installation, the existing installer already copies but I like the idea for speed and discoverability. I am going to take a look at how this is usually set up and whats needed. Should we do it within this PR or a separated one? thoughts? 🙂 |
Owner
|
Merging, have a cool stop hook for plan mode coming in as well #577 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
review,annotate, andlastWhy
Codex app does not accept
!commands in chat, so the current direct shell-style Plannotator invocations are awkward or unavailable in the app experience.There is also a workflow gap when Plannotator returns annotations in Codex CLI: the agent receives the feedback, but it does not proactively act on it unless the user sends another explicit follow-up message.
These skills help in both places:
$plannotator-*skillsScreenshots
Codex App - Skill execution and waiting responses:

Codex App - Receiving annotation and acting on it:

Scope notes
This PR focuses only on the user-invoked Codex flows that already map well to Plannotator today.
Test plan
apps/skills/