$ loading_
Trigger ADO CI pipelines for Copilot-created pull requests via PR comments.
This is an open-source, prompt-only skill with no executable package or installation steps in the provided material, so overall risk is low. It describes posting GitHub PR comments to trigger CI, but does not declare bundled secrets, endpoints, or local data access capabilities.
The material declares no required secrets or environment variables; the README only mentions optionally using an existing GITHUB_TOKEN, but the skill itself does not require or store credentials.
The system flags it as prompt-only and no remote endpoint is declared; while the README mentions posting comments to the GitHub API, this is operational guidance rather than an implemented automatic data egress path in the skill itself.
The provided content is textual guidance only, with no packaged code, install commands, or actual process-execution logic; it suggests using gh or curl, but does not show that the skill itself can execute local commands.
The material does not declare reading or writing local files, system resources, or broader repository data access; it is limited to instructions for commenting on a specified GitHub PR, with no sign of overbroad access.
The source points to an open-source Microsoft GitHub repository, which improves auditability; although 0 stars, no declared license, and unknown maintenance add some uncertainty, they do not amount to a high-risk supply-chain red flag.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "trigger-pipelines-for-copilot-pr" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/FluidFramework/main/.claude/skills/trigger-pipelines-for-copilot-pr/SKILL.md 2. Save it as ~/.claude/skills/trigger-pipelines-for-copilot-pr/SKILL.md 3. Reload skills and tell me it's ready
Please trigger the ADO pipeline for Copilot-created PR #128 by posting a /azp run comment on the pull request to start CI.
A trigger comment is posted on the specified PR, and the corresponding ADO CI pipeline starts.
Copilot just updated fix PR #342. Please retrigger the Azure DevOps validation pipeline for that PR using a /azp run comment.
The PR validation pipeline is retriggered so the latest commits can be checked by CI.
The user asked to run CI for Copilot-submitted pull request #57. Please trigger the relevant pipeline by posting a /azp run comment.
The relevant PR checks are started, launching the CI jobs configured in Azure DevOps.
Post the following two comments to the PR specified by the user ($ARGUMENTS), in the microsoft/FluidFramework repository on GitHub.
They need to be posted separately because otherwise it gets too long and
fails to trigger correctly.
First comment:
/azp run Build - protocol-definitions,Build - test-tools,server-gitrest,server-gitssh,server-historian,server-routerlicious,Build - client packages,repo-policy-check
Second comment:
/azp run Build - api-markdown-documenter,Build - benchmark-tool,Build - build-common,Build - build-tools,Build - common-utils,Build - eslint-config-fluid,Build - eslint-plugin-fluid
Posting those comments will trigger all our pipelines, which is necessary for PRs that are created by Copilot.
To post the comments first check if the GitHub CLI is available,
and if so use MSYS_NO_PATHCONV=1 gh pr comment <PULL_REQUEST_NUMBER> --repo microsoft/FluidFramework --body "<COMMENT_TEXT>".
Note: MSYS_NO_PATHCONV=1 is required on Windows (Git Bash) to prevent /azp from being expanded to C:/Program Files/Git/azp.
If gh is not available but $GITHUB_TOKEN is, you can try the GitHub REST API directly, e.g.:
curl -L \
-X POST \
-H "Accept: application/vnd.github+json" \
-H "Authorization: Bearer $GITHUB_TOKEN" \
-H "X-GitHub-Api-Version: 2022-11-28" \
https://api.github.com/repos/microsoft/FluidFramework/issues/PULL_REQUEST_NUMBER/comments \
-d '{"body":"<COMMENT_TEXT>"}'
If neither is available, don't do anything and tell the user you can't complete the request and why.
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.
Review code or branches for correctness, compatibility, architecture, tests, performance, and security.
Generate Fluid-style PR content, push branches, and open GitHub pull requests.
Validate Azure DevOps pipeline changes and troubleshoot builds and YAML faster.
Generate standardized Git commits from diffs with logical grouping support.
Connect AI to Azure DevOps to manage work items, repos, and pipelines.
Turn transcripts, text, and images into structured Azure DevOps work items.
Lets AI manage Azure DevOps projects, repos, work items, PRs, and pipelines.
Automate GitHub branches, tests, commits, pushes, and PRs with natural language.