How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
affaan-mCopilot instructionsaffaan-m/ECC/.github/copilot-instructions.md
test before the implementation; target 80%+ coverage. 4. **Review before committing** — check for security issues, code quality, and regressions. 5. **Conventional commits** — `feat`, `fix`, `refactor`, `docs`, `test`, `chore`, `perf
DietrichGebertCopilot instructionsDietrichGebert/ponytail/.github/copilot-instructions.md
efficiency), input validation at trust boundaries, error handling that prevents data loss, security, accessibility, the calibration real hardware needs (the platform is never the spec ideal, a clock drifts
MicrosoftCopilot instructionsmicrosoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
SupabaseCopilot instructionssupabase/supabase/.github/copilot-instructions.md
Threshold Only comment when you are **>85% confident** the issue is a real bug, security vulnerability, or logic error. If you are unsure, do not comment. Silence is better than
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.
