Browse Skills

Policy Check runs pnpm policy-check from the repo root to validate package compliance. Use it for a specific package with --path, or run the repository-wide check when changes may affect other packages.

Provides a structured approach to code review feedback: fetch comments, clarify requirements, implement one change at a time, run tests, and push. Emphasizes verification and quality over performative agreement.

Review checks a branch or diff for correctness, API compatibility, architecture, tests, performance, and security. Use it when you need a concise code review with optional deeper analysis.

Review PR Locally checks out an Azure DevOps or GitHub pull request into an isolated git worktree so a human can inspect it in their editor. It also posts only the review comments the human explicitly requests, using ADO tools or the gh CLI.

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

Captures screen context using platform-specific CLI tools and loads images for visual analysis. Use when asked to take a screenshot or analyze UI issues.

Defines a structured workflow for AI coding agents: checks for protected branches, sets operating modes (full-send or copilot), enforces research, planning, TDD, documentation, and strict coding guidelines.

A systematic four-phase debugging framework (root cause investigation, pattern analysis, hypothesis testing, and implementation) for when you encounter any bug, test failure, or unexpected behavior, ensuring you understand the issue before attempting fixes.

Follow a disciplined test-driven development cycle: write a failing test first, implement minimal code to pass, then refactor. Use for any feature or bugfix to ensure tests genuinely verify behavior.

Prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies. Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code.

Trigger Pipelines For Copilot PR posts two /azp run comments on a specified PR in microsoft/FluidFramework. Use it when a Copilot-created pull request needs Azure DevOps pipelines started.

After code changes, use this skill to update Noridocs—documentation files describing folder architecture and implementation—via an automated subagent.