Fluid Pr Skill for Claude
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".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/microsoft/FluidFramework --skill fluid-prWhat it tells the agent to use
found in the instruction textThe instruction itself
2 sections, as written by the author<required>
*CRITICAL* Do NOT run gh pr create until the user has explicitly confirmed via AskUserQuestion in step 5. Do not skip ahead.
*CRITICAL* Add the following steps to your task/todo list using your available task tooling (TaskCreate for Claude, TodoWrite for Copilot):
- Confirm you are NOT on
mainor 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. - Verify that the
originremote does not point tomicrosoft/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. - Load the
fluid-pr-guideskill 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. - Using the loaded
fluid-pr-guide, compose the PR title and body following its conventions and template. - Print the proposed title and body as text, then immediately use the
AskUserQuestiontool to let the user choose what to do next. Use these exact options: - "Create PR" — Push the branch and open the pull request
- "Create draft PR" — Push the branch and open a draft pull request
- "Edit" — Revise the title or body before creating
- "Cancel" — Don't create a PR
- If the user picks "Edit", apply their edits and re-present (go back to step 5). If "Create PR" or "Create draft PR", push and create accordingly. If "Cancel", stop.
</required>
Pushing and Creating the PR
Before pushing, verify that origin does not point to microsoft/FluidFramework. Run:
git remote get-url origin
If the URL contains microsoft/FluidFramework, stop — pushing a branch directly to the main repo is almost certainly not intended. Tell the user they likely need to push to their fork instead. 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
)"
# Create draft PR (option 2) — add the --draft flag
gh pr create \
--draft \
--title "<title>" \
--body "$(cat <<'EOF'
<body>
EOF
)"
After creating the PR, output the PR URL so the user can navigate to it.
Updating an existing PR description
You do not have permissions to edit PRs on the upstream microsoft/FluidFramework repo via the API. If you need to update an existing PR's title or body, write the new content to a temp file and tell the user to copy-paste it into GitHub:
cat <<'EOF' > "$TMPDIR/pr-body.md"
<new body content>
EOF
Then tell the user: "I can't edit the PR directly — I've written the updated description to $TMPDIR/pr-body.md. Please copy-paste it into the PR on GitHub."
Other skills for the same job
different authors, same section of the catalogue
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
GitHub CLI (gh) comprehensive reference for repositories, issues, pull requests, Actions, projects, releases, gists, codespaces, organizations, extensions, and all GitHub operations from the command line.
GitHub CLI - manage repositories, issues, pull requests, actions, releases, and more from the command line.
You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
How to use it
Take microsoft/fluid-pr from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.