Invoke selected Pi-native skills through native commands - #3253
Merged
SawyerHood merged 1 commit intoSep 8, 2026
Merged
Conversation
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.
Human comments
What was wrong
The Pi bridge discarded structured skill-mention metadata and forwarded only the picker’s
/namedisplay text. Pi requires/skill:nameto explicitly invoke native skills, so skills withdisable-model-invocation: truecould not be used through BB. This is tracked in #3246.What changed
The Pi bridge now recognizes exactly one validated, picker-selected skill mention and converts it into a leading
/skill:<name>command. All remaining prompt text becomes the skill arguments, regardless of where the chip appeared, while preserving argument whitespace and existing file/image input behavior.Plain slash text, provider commands, malformed mentions, and prompts containing multiple selected skills remain unchanged. The fake Pi harness gained an opt-in prompt dump used to verify that image payloads survive the transformation.
This supersedes #3249. That PR rewrites the selected token in place, so a mid-message selection becomes
text /skill:name arguments; Pi only expands/skill:nameat the beginning of its input. This change instead moves the semantic invocation to the front and passes the remaining text as arguments.This changes no wire protocol, persisted data, CLI surface, or skill-discovery behavior.
How you verified
openai-codex/gpt-5.6-terra, and a disposable native skill usingdisable-model-invocation: true.pnpm exec turbo run typecheck --filter=bb-plugin-provider-pipnpm exec turbo run test --filter=bb-plugin-provider-pi— 23 files and 133 tests passed.pnpm exec oxfmt --check plugins/provider-pi/src/bridge/bridge.ts plugins/provider-pi/src/bridge/bridge.skill-command.test.tsgit diff --checkFixes #3246