Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →fluid-pr
Use when creating a pull request in the Fluid Framework repo. Composes a PR title and body following Fluid Framework conventions, proposes them to the user, then pushes the branch and creates the PR on GitHub. Triggers on "create a PR", "make a PR", "open a PR", "submit a PR", or "push and create a PR".
5 of 22 test cases passed with the skill.
Tokens, turns and time describe resource use, not a dollar price.
Lift withheld: 6 comparable cases; this report requires 8.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I reviewed the PR proposal for branch `feature/id-compressor`, but I selected 'Cancel'. What happens next?
| Checked | Without skill | With skill |
|---|---|---|
| Stops the pull request creation process entirely without running git push or gh pr create | Missed | Passed |
The instructions your model reads when the skill loads.
CRITICAL Add the following steps to your task/todo list using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot):
main or any release branch. If you are, stop and tell the user: you cannot create a PR from a protected branch — they need to create or switch to a feature branch first.origin remote does not point to microsoft/FluidFramework. If it does, stop and tell the user: pushing a branch directly to the main repo is not allowed — they should push to their fork instead. Pipeline changes on branches prefixed with test/ are an exception.fluid-pr-guide skill NOW (via the Skill tool) before composing anything. It contains the title conventions, body template, and section guidance you need. Do NOT skip this step or rely on memory.fluid-pr-guide, compose the PR title and body following its conventions and template.AskUserQuestion tool to let the user choose what to do next. Use these exact options:
Before pushing, verify that origin does not point to microsoft/FluidFramework. Run:
git remote get-url origin
If the URL contains microsoft/FluidFramework, stop unless the branch is prefixed with test/ and the conversation context or changed files indicate that the change needs Azure Pipelines testing. A user request for a "test branch" in that context is sufficient intent to use the exception. Otherwise, tell the user they should push to their fork instead and do not proceed.
Once the checks in steps 1–2 pass silently, compose the title and body, print them as text, then use the AskUserQuestion tool with the four options as described in step 5. This is the only point where the fluid-pr flow asks the user a question.
# Push branch (first time)
git push -u origin <feature-branch>
# Create PR (option 1)
gh pr create \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)"
test cases passed with the skill
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.