Pull unmerged PlatformPlatform pull requests into a downstream project by cherry-picking each one onto the platformplatform-updates branch. Renames commits to "PlatformPlatform PR N - title" per the existing convention. Drives a ralph-loop that validates each commit (build, test, format, lint, optional e2e) before moving on. Use in downstream projects that have PlatformPlatform configured as the upstream remote.
SkillScore36Maintained
Automatic
◆Coding pack
Last verified 8/19/2026
What it changes
Passed 6 of 17 test cases with the skill, and 2 of 17 without it.
Without skill14%
With skill36%
Checks it passed that the model alone missed
Verifies current git branch is `platformplatform-updates`.
Creates the update branch off main branch rather than current detached HEAD.
Categorizes PRs touching downstream-diverged core files as likely adaptation.
and 13 more in the full report
8 fixed0 passed either way11 still failing3 broke
Pass-rate lift
+23 pp
Tokens
+101%
Agent turns
0%
Response time
-52%
Model gemini-3.6-flashMeasured 8/19/2026v18 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 8
Prompt
Our repository does not support git worktrees due to nested submodules. If I decline creating a worktree, what branch setup command should be executed before setting up tracking files?
What was checked, without and with the skill
Checked
Without skill
With skill
Executes `git switch --create platformplatform-updates main` when worktree creation is declined.
Missed
Passed
Creates the update branch off main branch rather than current detached HEAD.
Missed
Passed
case-08 · gemini-3.6-flash · 8/19/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md194 linessingle file
Pull PlatformPlatform Changes
Discover unported PlatformPlatform pull requests and emit a /ralph-loop:ralph-loop prompt that the user runs themselves to cherry-pick them one at a time. Optionally interviews the user upfront to capture porting decisions for each PR.
This skill assumes the current repo is a downstream project with upstream configured as the PlatformPlatform remote. The CLI command pull-platformplatform-changes will fail if the remote isn't set up — that's the expected guardrail.