Microsoft

@microsoftOpen source projects and samples from Microsoft

Open source projects and samples from Microsoft

Redmond, WA

microsoft.com

Curated from public sources. This profile has not been claimed.

GitHub sources1370 Skills · 102 repositories

102 sources

1370 standalone skills1370 published skills

Cloud Platforms

azure-scaffold-wizard

Scaffold a complete, production-ready Azure project from scratch for ANY use case: RAG chatbots, multi-agent systems, API backends, data pipelines, Azure Functions, full-stack web apps, ML training/inference, or event-driven microservices. USE FOR: gathering requirements through adaptive questioning, generating complete project folder structures with all source files, Azure Bicep infrastructure, azure.yaml for azd-up deployment, Docker configuration, CI/CD workflows, README with architecture diagrams, and Responsible AI documentation. Produces fully deployable Azure projects targeting Azure Co

AI Agents

trigger-pipelines-for-copilot-pr

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.

Application Security

review

Use when asked to review code, review a branch, or do a code review. Spawns Breaker (correctness) and API Analyst (compatibility/conventions) sub-agents while the orchestrator reviews architecture, tests, performance, and security.

Testing

review-pr-local

The authority on pulling a pull request — Azure DevOps or GitHub — into an isolated local worktree so a human can review it in their editor, and on posting human-controlled review comments back to the PR (ADO via the ado PR-thread MCP tools or the Azure DevOps REST API, GitHub via the gh CLI). Auto-detects the platform and all identifiers from the PR URL; not tied to any specific repository. The AI assists an interactive human review and only ever posts comments the human explicitly requests. If you find yourself checking out a PR branch over the user's own working tree, or posting AI-authored

Governance

policy-check

This skill should be used when the user asks to "run policy check", "check policy", "policy-check", or needs to validate package compliance. Provides guidance on running policy checks for specific packages or the entire repository.

Data Engineering

pipeline-test-triage

Triage test failures in an Azure DevOps pipeline run for Fluid Framework. Use when the user shares an ADO build/pipeline URL or build ID and wants failures analyzed, when they ask "why did this pipeline fail", "summarize the test failures", "is this test flaky or a real bug", "compare these runs", or wants bugs filed for genuine failures. Covers the Real Service End to End Tests pipeline as the worked example but applies to any FF test pipeline.

Testing

fluid-release

Fluid Framework client release group — minor releases, patch releases, and post-release type test updates. Covers release prep, branching, version bumps, changelogs, release notes, and type test baselines. In autonomous mode, auto-detects state from the schedule and repo, attempts to execute, and falls back to a GitHub issue on failure. Triggers on "release", "do the release", "release status", version bump, release notes, changelog, release branch, or release engineering.

Developer Tools

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".

Developer Tools

fluid-pr-guide

Use when composing, writing, drafting, or reviewing a PR title, PR description, or PR body in Fluid Framework — provides title style, body template, and section guidance.

Developer Tools

comparison-base

Internal reusable workflow for resolving the correct Git comparison base for branch reviews and change analysis. Finds the PR target or canonical Fluid Framework upstream, selects the newest shared target-history commit, and detects substantial divergence.

Backend

ci-readiness-check

Use when the user explicitly asks for a CI check or to push their branch — e.g. "ci readiness", "check ci", "pre-push check", "ready for CI", "ci check", "ready to push", "push my changes", "push the branch", "let's push". Catches common CI failures before pushing — formatting, stale API reports, missing changesets, policy violations.

Backend

api-changes

Use when customer-facing API changes were made — i.e., API report .md files differ from the branch's resolved comparison base. Guides through release tag assignment, API Council review requirements, breaking change classification, deprecation process, and changeset guidance. Triggered automatically by ci-readiness-check when api-report diffs are detected.

Planning

writing-plans

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

Testing

azure-scaffold-wizard

trigger-pipelines-for-copilot-pr

review

review-pr-local

policy-check

pipeline-test-triage

fluid-release

fluid-pr

fluid-pr-guide

comparison-base

ci-readiness-check

api-changes

writing-plans

webapp-testing

using-skills

using-screenshots

using-git-worktrees

updating-noridocs

testing-anti-patterns

test-driven-development

systematic-debugging

starting-nori

root-cause-tracing

receiving-code-review

azure-scaffold-wizard

trigger-pipelines-for-copilot-pr

review

review-pr-local

policy-check

pipeline-test-triage

fluid-release

fluid-pr

fluid-pr-guide

comparison-base

ci-readiness-check

api-changes

writing-plans

webapp-testing

using-skills

using-screenshots

using-git-worktrees

updating-noridocs

testing-anti-patterns

test-driven-development

systematic-debugging

starting-nori

root-cause-tracing

receiving-code-review