Use the canonical Pixeltable skill repository - #3
Merged
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
1 participant
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.
Pixelbot should consume Pixeltable guidance from its canonical repository instead of carrying a project-local copy that can drift.
This follow-up removes
.agents/skills/pixeltableandskills-lock.json, and points contributors tonpx skills add pixeltable/pixeltable-skillinAGENTS.md.It also fixes the only failed check from PR #2: Pixeltable 0.7.7 returns an error for
pxt service logson local services even though it prints the log path. CI now verifies and tails that local file directly before stopping the service. All other PR #2 checks passed, including Python 3.11-3.14, frontend, and clean package installation.