How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/microsoft-ui-xaml/src/.github/copilot-instructions.md
For detailed instructions on building and testing, see the skills defined in .github/skills/: - .github/skills/build/SKILL.md - Build commands and file-to-project mappings
MicrosoftCopilot instructionsmicrosoft/TinyTroupe/.github/copilot-instructions.md
This document provides the primary guidelines for generating programs in the TinyTroupe project. It is meant to complement any existing documentation or built-in knowledge. This document takes precedence over any other instructions or built-in knowledge, therefore you MUST follow these guidelines, ALWAYS. To make this very clear to the programmer, you should refer to the instructions given here (e.g.," ... as per my primary guidelines, I will avoid a complex solution to this problem, unless you explicitly ask me to…
Model Context ProtocolCopilot instructionsmodelcontextprotocol/registry/.github/copilot-instructions.md
The data/seed.json file is seed data for local development only. Do NOT create pull requests that add or modify server entries in data/seed.json to publish a server. To publish an…
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
No summary in the file. Open it to read it.
MicrosoftCopilot instructionsmicrosoft/vscode-docs/blogs/2025/03/.github/copilot-instructions.md
This project is a web application that allows users to create and manage tasks. The application is built using React and Node.js, and it uses MongoDB as the database.
MicrosoftCopilot instructionsmicrosoft/vscode-docs/.github/copilot-instructions.md
Follow the documentation writing guidelines when reviewing or writing documentation.
MicrosoftCopilot instructionsmicrosoft/rushstack/.github/copilot-instructions.md
You are a Rush monorepo development and management expert. Your role is to assist with Rush-related tasks while following these key principles and best practices: The standard directory structure for…
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
Multi-language monorepo for runtime governance of AI agents. Core is Python, with SDKs in TypeScript, Rust, .NET, and Go. Core Python packages live under packages/: Language SDKs: Other top-level directories: docs/ (MkDocs site), examples/ (runnable integrations), demo/ (live dashboards), pipelines/ (ESRP release automation), benchmarks/, fuzz/ (ClusterFuzzLite), notebooks/. Each subdirectory with an AGENTS.md has area-specific commands and boundaries: read it before changing code there. For major design changes, always ask a maintainer (a collaborator with the Maintain or Admin role) before…
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/.github/copilot-instructions.md
When reviewing pull requests, follow these rules strictly. Before reviewing any file, CHECK if it matches these patterns:
Microsoft AzureCopilot instructionsAzure/Azure-Sentinel/Tools/Microsoft-Sentinel-Classic-CLv1-Tables-Impact-Assessment/.github/copilot-instructions.md
These instructions apply to all Copilot interactions in this repository. They provide context about the project, coding conventions, and domain knowledge so that Copilot can give accurate, relevant assistance. PowerShell tool that discovers classic V1 custom log tables (CLv1) in a Microsoft Sentinel / Log Analytics workspace, assesses dependency impact across all content types, and maps tables to Content Hub solutions with connector classification. The HTTP Data Collector API retires September 14, 2026. All classic custom log tables must migrate…
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-net/.github/copilot-instructions.md
Note: For general AI agent guidelines and repository overview, see AGENTS.md at the repository root. This repo contains Azure SDKs for various Azure services and tools that generate them. For detailed workflow instructions, see SDK Release. Before committing changes to SDK packages under sdk/, always run the pre-commit validation checks described in the pre-commit-checks skill. These checks run dotnet format, regenerate public API listings, update snippets, and regenerate code as needed. They may produce additional file changes that must be…
FlorianBruniauxCopilot instructionsFlorianBruniaux/claude-code-ultimate-guide/.github/copilot-instructions.md
Use /CLAUDE.md as the single source of truth for this repository. Key expectations: - Follow the repository rules and workflows defined in /CLAUDE.md. - Update CHANGELOG.md under [Unreleased] for any…
MicrosoftCopilot instructionsmicrosoft/typespec/.github/copilot-instructions.md
ALWAYS follow these instructions first and only fall back to additional search and context gathering if the information here is incomplete or found to be in error. TypeSpec is a language for defining cloud service APIs and shapes. This monorepo contains the TypeSpec compiler, standard library packages, tools, documentation, and various language client emitters. [!IMPORTANT] These instructions do NOT apply to the language emitter packages (http-client-csharp, http-client-java, http-client-python). Those packages are excluded from the pnpm workspace and do not require…
MicrosoftCopilot instructionsmicrosoft/typespec/packages/http-client-java/.github/copilot-instructions.md
See http-client-java-development for instructions on how to develop the TypeSpec library for Java client.
MicrosoftCopilot instructionsmicrosoft/typespec/packages/http-client-js/.github/copilot-instructions.md
Scope: These instructions apply only to the packages/http-client-js sub-project in this monorepo. Use them whenever Copilot generates code, tests, commit messages, or pull request descriptions for the emitter. If Copilot is used in other sub-projects, these rules do not apply unless stated otherwise. - Project Purpose We are building a TypeSpec Emitter that generates JavaScript (TypeScript) HTTP clients.
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-python/.github/copilot-instructions.md
Note: For general AI agent guidelines and repository overview, see AGENTS.md at the repository root. REFERENCE DOCUMENTATION: - Official pylint guide - Tool usage guide REFERENCE SOURCES: - Azure pylint guidelines - Pylint documentation ALLOWED ACTIONS: ✅ Fix warnings with 100% confidence ✅ Use existing file for all solutions ✅ Reference official guidelines FORBIDDEN ACTIONS: ❌ Fix warnings without complete confidence ❌ Create new files for solutions ❌ Import non-existent modules ❌ Add new dependencies/imports ❌ Make unnecessary large changes…
MicrosoftCopilot instructionsmicrosoft/azurelinux/.github/copilot-instructions.md
Azure Linux is a TOML-defined Linux distribution that imports RPM specs from upstream distros (primarily Fedora) and customizes them via an overlay system — no spec forking required. The azldev CLI tool drives all component and image workflows. One of the core tenets of this project is minimal necessary divergence from upstream. Overlays should be surgical and only change what's needed to meet Azure Linux requirements. Upstream packages should be preferred over bespoke components, and local specs should be a…
GitHubCopilot instructionsgithub/gh-aw/.squad/templates/copilot-instructions.md
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines. IMPORTANT — run this check on EVERY session start, before doing any work: Inspect your agent_instructions for the coordinator canaries. This is a two-state payload-integrity check within a known Squad coordinator session; it verifies whether the coordinator payload loaded fully or was visibly truncated. It is not proof that an agent with no canaries is safely non-Squad — wholly…
vitali87Copilot instructionsvitali87/code-graph-rag/.github/copilot-instructions.md
When reviewing pull requests: - Only leave comments for critical, major, or high-severity issues: logic bugs, security vulnerabilities, data loss or corruption, race conditions, and breaking API changes. - Do NOT comment on code style, formatting, naming, comments/docstrings, or minor/optional refactoring suggestions — linters handle those. - If no issue meets that bar, do not leave any inline comments.
entireioCopilot instructionsentireio/cli/.github/copilot-instructions.md
Entire CLI is a Go CLI tool that captures AI coding agent sessions (Claude Code, Codex, Antigravity, OpenCode, Cursor, Factory AI Droid, Copilot CLI, etc.) as searchable metadata stored separately from code commits. It uses a strategy pattern for session/checkpoint management with minimal impact on commit history. Tech Stack: Go (version in mise.toml), Cobra (CLI), charmbracelet/huh (interactive prompts), go-git/v5 (with caveats) All commands use mise as the task runner. Always run these in order before committing: CI runs these checks…
Repository-wide instructions for GitHub Copilot, kept in .github/copilot-instructions.md.
How to build and test, the project's structure, and the conventions Copilot should follow in suggestions and reviews.
No. Copilot's coding agent also reads AGENTS.md, so many projects keep the shared rules there.
Open a file to see its discussion. Reports from people and their agents are coming.
