How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Microsoft AzureCopilot instructionsAzure/PSDocs.Azure/.github/copilot-instructions.md
Copilot Instructions for PSDocs.Azure Monorepo ## Code Review Guidelines When performing a code review, prioritize CI/CD correctness, build scripts, and monorepo structure changes. ### Focus review comments on: - `build.ps1` - Root build orchestrator
MicrosoftCopilot instructionsmicrosoft/winget-studio/.github/copilot-instructions.md
bodies; open a pull request or link a branch when code is available. - Before opening a pull request, review `CONTRIBUTING.md`, follow the PR template, keep the change focused, and summarize
anchildress1Copilot instructionsanchildress1/awesome-ai/.github/copilot-instructions.md
Code Reviews Refer to [AGENTS.md](../AGENTS.md) for all repo standards
MicrosoftCopilot instructionsmicrosoft/omnichannel-chat-sdk/.github/copilot-instructions.md
tests to verify functionality - **Error Handling**: Handle errors gracefully with proper telemetry logging - **Review Process**: Code must be reviewed by at least one other developer before merging ### Omnichannel Chat
stbenjamCopilot instructionsstbenjam/skillsaw/.github/copilot-instructions.md
benchmarks/` (`make benchmark`, `make profile`, `make benchmark-save` / `make benchmark-compare` for regression checks — review `DEVELOPMENT.md`). When touching content rules, the lint tree, or `utils.py` read paths, save a baseline
ahmed3elshaerCopilot instructionsahmed3elshaer/everything-claude-code-mobile/.github/copilot-instructions.md
where applicable. Useful workflows: - Feature delivery: `feature-builder` skill or `/feature-build` in Claude Code. - Android review: `android-patterns`, `jetpack-compose`, and `mobile-testing`. - iOS review: `swift-patterns`, `swiftui-patterns
avelinoCopilot instructionsavelino/mcp/.github/copilot-instructions.md
pool.acquire()` — never hold `Arc ` across await points. ### Review Checklist for DB Changes When reviewing code that touches ChronDB: - [ ] Key prefix is unique and documented in the table above - [ ] Serialization round
swimmwatchCopilot instructionsswimmwatch/cloakbrowser-mcp/.github/copilot-instructions.md
Repository Instructions Follow `AGENTS.md` for project-wide coding, testing, documentation, changelog, and commit rules. For release preparation, publishing, verification, or recovery tasks, read `.agents/skills/project-release/SKILL.md` before making changes. That file
deploystackioCopilot instructionsdeploystackio/deploystack/.github/copilot-instructions.md
independent changelog generation - Scoped commits ensure proper release automation - Clear impact assessment for code reviews - Enables independent service versioning ## Code Generation Guidelines - Follow TypeScript best practices across all services
MicrosoftCopilot instructionsmicrosoft/Agent365-devTools/.github/copilot-instructions.md
sentence rationale. Keep the `(#NNN)` reference; fix any sibling entry the change makes stale. ### Code Review Mindset - Be cautious about deleting code; avoid `git restore` without review - Do not create
bug-opsCopilot instructionsbug-ops/zeph/.github/copilot-instructions.md
applyTo: "**" --- # Copilot Code Review Instructions ## Project Context Zeph is a Rust AI agent workspace (Edition 2024, resolver 3) with 31 library crates under `crates/` plus the `zeph` CLI binary. Review
MicrosoftCopilot instructionsmicrosoft/terraform-provider-power-platform/.github/copilot-instructions.md
style and help contributors produce high-quality, consistent code. Always consider existing patterns in the repository—when in doubt, review similar resources or tests for reference and keep
ohad6kCopilot instructionsohad6k/VibeRaven/.github/copilot-instructions.md
viberaven clean --plan` to create a reviewable cleanup plan. - Provider dashboard checks are not cleared by repo-code edits. Billing/product configuration, DNS, webhooks, credentials, quotas, and live provider verification must
MicrosoftCopilot instructionsmicrosoft/wmi/.github/copilot-instructions.md
working on a pull request, **DO NOT** mark the PR as ready for review until all of the following conditions are met: 1. **All CI/CD pipelines must pass**: Wait
spboyerCopilot instructionsspboyer/sensei/.ai-team-templates/copilot-instructions.md
check your capability profile in `.ai-team/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
MicrosoftCopilot instructionsmicrosoft/BC-Bench/.github/copilot-instructions.md
setup, but use different prompts, expected outputs, and evaluation pipelines. Future categories such as `code-review` can be added within the same overall benchmark structure, though they may require different
schmitthubCopilot instructionsschmitthub/clawker/.github/copilot-instructions.md
Copilot code review instructions You review pull requests for this repository. `AGENTS.md` at the repository root, the package `AGENTS.md` files, and the Serena memories under `.serena/memories/` are the coding standard
0xmariowuCopilot instructions0xmariowu/AgentLint/.github/copilot-instructions.md
wrapper is shell + JS, published to npm. Any Copilot agent (Coding Agent, Code Review, ci-doctor) working on this repo must follow the rules below. ## Hard rules — never violate
MicrosoftCopilot instructionsmicrosoft/mssql-rs/.github/copilot-instructions.md
with: ```bash ./setup-hooks.sh ``` ## Code Quality — No AI Slop - No verbose comments restating what the code does — Rust is expressive enough - No filler phrases: "This ensures that...", "In order
naviktCopilot instructionsnavikt/copilot/.github/copilot-instructions.md
rename variables, restructure working code, or refactor beyond the task at hand. Keep diffs small and focused so they are easy to review. ### Kotlin/Ktor Patterns - ApplicationBuilder pattern for bootstrapping - Sealed
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.
