Add propagate-pr skill for cross-repo PR propagation#1283
Draft
Add propagate-pr skill for cross-repo PR propagation#1283
Conversation
Adds a Claude Code skill that takes a PR URL, fetches its diff, and propagates the changes to other MUI repositories using git worktrees. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Replace `gh pr diff --stat` with `--name-only` (--stat not supported) - Require "origin" as push remote instead of picking first non-mui remote - Scope gh allowed-tools to specific subcommands Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Bundle size report
Check out the code infra dashboard for more information about this PR. |
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
Adds a
/propagate-pr <pr-url>Claude Code skill that automates propagating a PR's changes across MUI repositories. It fetches the diff (excluding lockfiles), asks the user which repos to target, then launches parallel agents that create git worktrees, apply the diff, resolve conflicts, run validation, and push. PRs are only opened after explicit user confirmation. Helper Node.js scripts handle PR fetching, remote inspection, and worktree setup in parallel to keep things fast.