$ loading_
Generate Fluid-style PR content, push branches, and open GitHub pull requests.
This appears to be an open-source, prompt-oriented PR workflow skill with no declared secrets or fixed remote endpoints, so overall risk is low. However, its instructions explicitly involve git push and gh pr create; if the host agent has such tool capabilities, it would interact with code hosting services and perform repository write actions, so it should be used with user confirmation and least privilege.
No API keys, tokens, or environment variables are declared; the skill text does not ask the user to supply credentials. Any authentication would likely come from an already configured host git/GitHub CLI environment rather than from additional secret collection by this skill.
The README instructs pushing a branch and creating a GitHub PR, which implies routine outbound transfer of branch and PR content to a code hosting platform. No fixed hosts are declared, but the destination is function-related and expected; no unrelated or unknown endpoints are indicated.
The README explicitly includes commands/steps such as git remote get-url, git push, gh pr create, and writing a temp file, indicating local command execution and repository write actions if run by an agent with tool access. This is a normal capability for this class of tool, and no red flags suggest requests for elevated system privileges.
To generate and create a PR, the skill would access the current repository state, remote configuration, and proposed PR title/body, and may write a temp file for PR content. This access scope is broadly aligned with its stated purpose, with no indication of broad reads of unrelated local data.
System checks indicate this is prompt-only and open-source; the source points to a Microsoft-associated GitHub repository, making the content auditable and materially lowering supply-chain risk. One caveat is that the linked repository appears to be the broader project repo rather than a standalone release unit for this specific skill, and star/maintenance signals are limited, so verifying actual commit history is still advisable.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "fluid-pr" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.claude/skills/fluid-pr/SKILL.md 2. Save it as ~/.claude/skills/fluid-pr/SKILL.md 3. Reload skills and tell me it's ready
Create a PR for the Fluid Framework repo. Generate a convention-compliant PR title and body from the current branch changes, show them to me for confirmation, then push the branch and create the PR on GitHub.
It first proposes a repository-compliant PR title and body, then pushes the branch and returns the PR link after confirmation.
I just fixed a bug in Fluid Framework. Help me submit a PR by drafting a clear title, summary, and testing notes from the changes, then create the GitHub PR.
It produces a well-structured PR description with change and testing details, then creates the pull request.
Push the current branch and create a PR. Write the title and body following Fluid Framework conventions, and ask me for missing details first if needed.
It generates standardized PR copy, asks for any missing details when necessary, and completes the push-and-open workflow.
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.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 — 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.
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."
Create a custom skill with structure, documentation, and optional bundled scripts.
Trace errors backward through execution paths to identify the true root cause.
Update technical documentation after code changes are completed.
Explains how to use abilities effectively before starting any conversation.
Break large, long-running tasks into manageable chunks and preserve context.
Turn rough ideas into actionable designs through structured questioning and validation.
Draft and review Fluid Framework PR titles and descriptions consistently.
Create a pull request from the current session's code changes.
Create a draft pull request from the current session’s code changes.
Finalize completed work by committing, pushing, and opening reviewed pull requests.
Update an existing pull request with new changes from the current session
Run Fluid client releases with branching, versioning, changelogs, and release notes.