Sync magpie-setup bootstrap skill to current apache-magpie framework#69209
Merged
Merged
Conversation
The committed magpie-setup bootstrap is the only apache-magpie framework skill checked into this repo; every other skill is a gitignored symlink resolved from the local snapshot. Contributors running /magpie-setup load whatever bootstrap version is committed here, so it must track the framework as it advances. This refreshes it to the current framework tip (the apache-steward to Apache Magpie rename train), keeping a fresh clone's adoption flow aligned with the framework version the project pins.
potiuk
requested review from
amoghrajesh,
bugraoz93,
choo121600,
kaxil,
shahar1 and
vincbeck
shahar1
approved these changes
Jul 1, 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
2 participants
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.
Refreshes the committed
magpie-setupbootstrap skill from the apache-magpieframework snapshot (the only framework skill checked into the repo — all
others are gitignored symlinks). Brings it to the current framework tip,
which includes the apache-steward to Apache Magpie rename.
No behaviour change for anyone not running
/magpie-setup; the snapshot,symlinks, and local hooks are all gitignored and untouched by this diff.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8 1M) following the guidelines