How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/XBOX-Godot-Sample/.github/copilot-instructions.md
worktree that has drifted from main is not ready to be reviewed. Run `git fetch origin && git merge --ff-only origin/main` (or `git rebase origin/main`) before opening or refreshing
MicrosoftCopilot instructionsmicrosoft/AzureTRE/.github/copilot-instructions.md
Terraform to provision the actual resources in Azure. Common practices include: - Breaking Terraform code into modules - Using remote state for complex deployments - Applying proper tagging for cost tracking - Using variables.tf
ffrolivaCopilot instructionsffroliva/gflow-cli/.github/copilot-instructions.md
Copilot Code Review Instructions Review this repository as a Python CLI that automates browser-authenticated Google Flow workflows. Treat auth, browser automation, CI, release, and secret handling changes as high
Microsoft AzureCopilot instructionsAzure/fleet/.github/copilot-instructions.md
Copilot Instructions ## Build, Test, and Lint Commands ```bash make build # Build all binaries make reviewable # Run all quality checks (fmt, vet, lint, staticcheck, tidy) — required before PRs make lint # Fast
MicrosoftCopilot instructionsmicrosoft/sarif-sdk/.github/copilot-instructions.md
agent contributing to this repo, read these first — they capture the code-review notes that come up most often. ## ReleaseHistory.md style `ReleaseHistory.md` is **release notes**, not a PR description. Each
yennanliuCopilot instructionsyennanliu/InvestSkill/.github/copilot-instructions.md
clone https://github.com/yennanliu/InvestSkill.git cd InvestSkill ``` 2. **Open in your editor:** - **VS Code**: `code .` - **JetBrains IDE** (IntelliJ, PyCharm, etc.): Open the folder - **GitHub.com Web Editor**: Click `.` key in any GitHub
Conceptual-MachinesCopilot instructionsConceptual-Machines/magda-core/.github/copilot-instructions.md
GitHub Copilot Review Instructions for Magda This document defines code review guidelines for the Magda project, a JUCE/C++ audio DAW framework. Reviews should focus on critical bugs, performance improvements
timothywarner-orgCopilot instructionstimothywarner-org/claude-code/.github/copilot-instructions.md
server implementations. Key components include: - **Claude Code CLI**: Terminal-based workflows for code review, refactoring, and automation. - **MCP Memory Server**: Persistent memory for decisions, entities, and relationships. - **Custom Skills**: Reusable
jonathan-vellaCopilot instructionsjonathan-vella/apex/.github/copilot-instructions.md
review thread management or bulk GraphQL queries). In devcontainers, do not run `gh auth` commands unless the user explicitly asks for CLI auth troubleshooting. Git normally uses VS Code-forwarded
MicrosoftCopilot instructionsmicrosoft/vs-solutionpersistence/.github/copilot-instructions.md
Copilot instructions for this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Run the `.github/Prime-ForCopilot.ps1` script (once) before running any `dotnet
azrtydxbCopilot instructionsazrtydxb/procoder/.github/copilot-instructions.md
discipline of a senior developer. The `procoder` binary computes; you act. It never modifies code behind your back, and a file it could not check is never reported as clean
FerroxLabsCopilot instructionsFerroxLabs/ijfw/copilot/copilot-instructions.md
improve adjacent code, comments, or formatting. No speculative features. No abstractions for single-use code. Simplest solution that works. Self-verify before destructive or irreversible actions. Plan before complex tasks
vasylenkoCopilot instructionsvasylenko/bear-notes-mcp/.github/copilot-instructions.md
When performing a code review for a PR ## Review Objective - Perform the PR review as instructed in the "Review Guidelines" section below. - Be specific, concise, and actionable in your feedback
AMD-AGICopilot instructionsAMD-AGI/Hyperloom/.github/copilot-instructions.md
Copilot code-review instructions (Hyperloom) Advisory review. Flag only what static gates can't. ## What to review for - **Correctness / semantic edge cases**: null/empty/boundary inputs, off-by-one, unhandled `None`, silent
MicrosoftCopilot instructionsmicrosoft/MicroHack/03-Azure/01-04-AI/01_Agentic_SDLC/.github/copilot-instructions.md
src/docs/sqlite-integration.md` for deeper details. Avoid restating them in reviews and link instead. ## General Review Guidance When generating suggestions: 1. Prefer incremental, minimal diffs; preserve existing style and naming. 2. Surface
MicrosoftCopilot instructionsmicrosoft/vscode-cosmosdb/.github/copilot-instructions.md
symbols out of the translation key.** Emoji and other decoration should be concatenated in code, not embedded in the key — e.g. `'❌ ' + l10n.t('Command failed:')`, not `l10n.t('❌ Command failed
KbWenCopilot instructionsKbWen/agentic-os/.github/copilot-instructions.md
truth for this repository's agent behavior. Keep this file short because Copilot code review reads only the early portion of custom instruction files. ## Always Apply - Follow `AGENTS.md ## Review guidelines
thomast1906Copilot instructionsthomast1906/github-copilot-agent-skills/.github/copilot-instructions.md
nights and weekends - Monitor costs with budgets and alerts - Regular cost reviews with `cost-optimization` skill ## Infrastructure as Code **Preferred: Bicep** (for Azure-only projects) - Cleaner syntax than ARM templates
MicrosoftCopilot instructionsmicrosoft/vscode-black-formatter/.github/copilot-instructions.md
tests pass before submitting changes. - Always ensure documents and code are linted before submitting. - Do multiple rounds of review and refinement. - Do not feature creep — keep changes focused
MicrosoftCopilot instructionsmicrosoft/durabletask-dotnet/.github/copilot-instructions.md
tests in the same project or classes to which new tests are being added. ## Code Review Guidelines When reviewing code, follow these guidelines: - Provide all review comments in a single
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.
