trigger-pipelines-for-copilot-pr
Automates CI pipeline triggers for GitHub pull requests.
Install
mkdir -p .claude/skills/trigger-pipelines-for-copilot-pr && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/11937" && unzip -o skill.zip -d .claude/skills/trigger-pipelines-for-copilot-pr && rm skill.zipInstalls to .claude/skills/trigger-pipelines-for-copilot-pr
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Trigger ADO pipelines for a Copilot-created PR by posting /azp run comments. Use when the user asks to trigger CI pipelines for a specific PR.Key capabilities
- →Trigger FluidFramework build pipelines
- →Trigger FluidFramework test-tools pipelines
- →Trigger FluidFramework server-gitrest pipelines
- →Trigger FluidFramework repo-policy-check pipelines
- →Trigger FluidFramework api-markdown-documenter pipelines
- →Trigger FluidFramework build-tools pipelines
How it works
The skill posts two separate comments containing `/azp run` commands to a specified GitHub pull request in the `microsoft/FluidFramework` repository, which triggers the associated ADO pipelines.
Inputs & outputs
When to use trigger-pipelines-for-copilot-pr
- →Trigger CI for Copilot PR
- →Start automated build pipelines
About this skill
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.
When not to use it
- →When GitHub CLI is not available and GITHUB_TOKEN is not set
- →When the PR is not for the `microsoft/FluidFramework` repository
- →When the user wants to post a single comment with all commands
Limitations
- →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.
- →If neither is available, don't do anything and tell the user you can't complete the request and why.
How it compares
This skill automates the process of triggering specific ADO pipelines for Copilot-created PRs by posting pre-defined comments, unlike manual comment entry.
Compared to similar skills
trigger-pipelines-for-copilot-pr side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| trigger-pipelines-for-copilot-pr (this skill) | 0 | 4mo | Review | Beginner |
| turborepo | 61 | 2mo | Review | Intermediate |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
| ml-pipeline-workflow | 9 | 5mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by microsoft
View all by microsoft →You might also like
turborepo
vercel
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
ml-pipeline-workflow
wshobson
Build end-to-end MLOps pipelines from data preparation through model training, validation, and production deployment. Use when creating ML pipelines, implementing MLOps practices, or automating model training and deployment workflows.
linkerd-patterns
wshobson
Implement Linkerd service mesh patterns for lightweight, security-focused service mesh deployments. Use when setting up Linkerd, configuring traffic policies, or implementing zero-trust networking with minimal overhead.
deployment-pipeline-design
wshobson
Design multi-stage CI/CD pipelines with approval gates, security checks, and deployment orchestration. Use when architecting deployment workflows, setting up continuous delivery, or implementing GitOps practices.
glab
NikiforovAll
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.