Repository navigation
skills: Clarify public API sync output - #216
Merged
Merged
Conversation
![foxglove-beefcake[bot]](https://avatars.githubusercontent.com/in/5305709?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Mo-Elshenawy1
approved these changes
Nov 7, 2026
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.
Changelog
None
Docs
None
Description
The API sync skill prohibits private implementation details in public output, but its source-link and revision instructions leave that boundary ambiguous. Clarify that public artifacts should describe public API and Python client behavior, allow public references and Foxglove Linear issue links while excluding other non-public URLs, and keep private source revisions out of branch names and public output. Add a final check for internal details before delivery.
Validation: skill validation and
git diff --checkpassed. No runtime behavior changes.Source-link and revision instructions could conflict with the public-content rule.
Public references and behavior descriptions are required, with an exception for Linear issue IDs and short links used for tracking and issue closure; private source revisions remain in the private conversation.
BFCK-588
[ GENERATED BY AI ]