183 skills ・ Official · GitHub Copilot · sorted by popularity
Review Spec Kit code changes against relevant design documents, tests for expected and unwanted behavior, evidence that bug fixes prevent recurrence, and repository terminology. Findings identify the document sections behind design mismatches.
Process GitHub issues submitted for Spec Kit community extensions. Validate release details and required files, add or update the catalog and documentation table, and prepare a pull request with a validation summary.
Edit patch release notes for GitHub Enterprise Server, correcting typos and style while preserving approved technical facts. Keep repeated notes consistent across versions and update known issue source comments so future releases inherit the same edits.
Edit and validate Bazel build settings using conventions specific to CodeQL development. Follow established helpers for packaging and operating system differences, add dependencies with checksums, and check changed targets while respecting the standalone build setup.
Maintain reference test data and expected results for model-routing audits, which analyze how AI models are selected. Investigate mismatches, update outputs after intentional behavior changes, and add captured workflow runs as new test cases.
Guide visual changes to an existing documentation site and landing page. Apply defined limits for text width, spacing, navigation, and color so layout updates preserve readable content and a consistent visual style.
Turns collected repository statistics into an eight-panel PNG infographic. It shows pull request outcomes, timing, code changes, and human versus agent activity, with scripts to recalculate figures and check them against available source records.
Review cross-platform code and Git commands for filename, path, and shell compatibility issues. Apply shared timestamp utilities, platform-aware path handling, and file-based commit messages when working across Windows, macOS, and Linux.
Review technical claims and deliverables by checking evidence and testing alternative explanations. Confirm that references and API endpoints exist, then report verified, unverified, or contradicted claims alongside evidence and an overall review verdict.
Keep tests aligned with API changes and actual project files. This skill guides agents to update related tests in the same commit, refresh expected counts and lists, and check stale assertions when automated checks fail.
Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.
Draft and revise public replies to questions, bug reports, and community discussions. Use a warm, conversational tone while giving specific explanations, acknowledging uncertainty, asking focused follow-up questions, and making the next action clear.
Follow Squad's Git workflow from issue branches through pull requests and cleanup. It covers development from dev, isolated directories for parallel issues, coordinated changes across repositories, and promotion to preview, insiders, and stable releases.
Find unanswered GitHub issues and discussions, read their full conversations, and prepare response drafts. Organize drafts by response type and confidence for human review, with action logs and commands that help people post approved replies.
Extract lessons from corrections, praise, and unexpected cases in conversations. Organize findings by confidence level and propose updates to individual agent histories or shared team decisions, with changes shown for approval before saving.
Learn how to start an AI team with Squad in Copilot CLI. This reference explains how to invoke the coordinator agent, find the command catalog, and initialize a new project while avoiding common invocation mistakes.
Capture interface or documentation pages with Playwright and embed the screenshots in a GitHub pull request description. Reviewers can inspect visual changes without checking out the branch, using images hosted on a temporary branch.
Coordinate independent Squad AI teams across repositories using procedures for questions, review requests, and task delegation. Choose between direct CLI sessions, reading team metadata, and asynchronous requests based on repository access and task needs.
Validate changes to Squad coordinator and agent templates through real sessions using a locally built CLI. Check generated files, agent behavior, and saved state, then record evidence, scenario verdicts, and progress for pull request reviews.
Switch automatic model selection to lower-cost options for agent tasks, either for one session or through a saved setting. Explicit model choices remain in effect, while architecture and security review tasks use a separate economy selection.
Add checks to npm release workflows for version formats, authentication tokens, delayed package availability, and draft releases. The skill also covers preventing build scripts from unexpectedly changing release versions.
Document project-specific development rules for an AI agent using a starter template. It provides sections for error handling, testing, code style, file organization, examples, and practices to avoid, ready to fill with actual conventions.
Choose how an AI team handles each task, from a direct coordinator answer to parallel work by several agents. Includes decision criteria, example requests, and a short assignment template for small tasks.
Document responses to GitHub pull request reviews by replying to each comment thread after fixes are pushed. Connect feedback to specific changes and commits, explain rejected suggestions, and selectively resolve automated review threads.