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
MicrosoftCopilot instructionsmicrosoft/playwright/.github/copilot-instructions.md
Guidelines When reviewing pull requests: - Only comment on semantically meaningful issues: bugs, incorrect logic, security problems, or API contract violations. - Skip style, formatting, naming, and whitespace observations unless they cause
headroomlabs-aiCopilot instructionsheadroomlabs-ai/headroom/.github/copilot-instructions.md
text should be called out. 4. For user-facing, release, dependency, workflow, or security-sensitive changes, prefer blocking feedback over optional suggestions. 5. Focus on correctness, safety, and whether
aaif-gooseCopilot instructionsaaif-goose/goose/.github/copilot-instructions.md
confusing" - stay silent unless HIGH confidence it will cause problems ## Priority Areas (Review These) ### Security & Safety - Unsafe code blocks without justification - Command injection risks (shell commands, user input) - Path traversal
amruthpillaiCopilot instructionsamruthpillai/reactive-resume/.github/copilot-instructions.md
full|wenyan-ultra Stop: "stop caveman" or "normal mode" Auto-Clarity: drop caveman for security warnings, irreversible actions, user confused. Resume after. Boundaries: code/commits/PRs written normal
ToolJetCopilot instructionsToolJet/ToolJet/.github/copilot-instructions.md
Lucide React (`lucide-react`). Do NOT add new icon packages. - Static assets: `frontend/assets/images/`. ## Security - No API keys/secrets in client-side code. - Backend: parameterized queries only, never concatenate user input into
mukul975Copilot instructionsmukul975/Anthropic-Cybersecurity-Skills/.github/copilot-instructions.md
Facts - **Type**: Open-source cybersecurity skills library + framework mapping hub - **Skills**: 817 across 29 security domains - **Frameworks**: 6 (MITRE ATT&CK v14, NIST CSF 2.0, MITRE ATLAS, MITRE D3FEND, NIST
MongoDBCopilot instructionsmongodb/mongo/.github/copilot-instructions.md
Copilot instructions for this repository ## Flag likely CVE / security-vulnerability fixes Commits on `master` are automatically synced to the public `mongodb/mongo` repository. A security fix that lands on `master` before
gastownhallCopilot instructionsgastownhall/beads/.github/copilot-instructions.md
when creating issues. Issues without descriptions lack context for future work. ### Priorities - `0` - Critical (security, data loss, broken builds) - `1` - High (major features, important bugs) - `2` - Medium (default, nice
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
between builds when possible - **Yarn Cache**: Dependencies are cached globally to speed up installs ## Security Notes - Never commit secrets to source code - Use environment variables for configuration - Default admin token
InsForgeCopilot instructionsInsForge/InsForge/.github/copilot-instructions.md
integration tests for API endpoints - Maintain test coverage above 70% - Mock external dependencies appropriately ## Security Considerations - Never commit secrets or API keys - Use environment variables for configuration - Implement proper authentication
MicrosoftCopilot instructionsmicrosoft/GSL/.github/copilot-instructions.md
system (3.14+) - Google Test for unit testing - Support for multiple compilers (MSVC, GCC, Clang) ## Security Considerations - Bounds checking is a core principle - enforce it consistently - Design for safety while minimizing
MicrosoftCopilot instructionsmicrosoft/agent-governance-toolkit/.github/copilot-instructions.md
packages or modules that change the repo structure - Cross-cutting changes spanning 3+ packages - Security model changes (identity, trust, policy engine) - Breaking API changes to public interfaces - New framework integrations
MicrosoftCopilot instructionsmicrosoft/azurelinux/.github/copilot-instructions.md
keeps maintenance overhead low and makes it easier to pull in new versions and security updates from upstream. While AZL derives from Fedora, it is also an enterprise focused distro
vitali87Copilot instructionsvitali87/code-graph-rag/.github/copilot-instructions.md
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
MicrosoftCopilot instructionsmicrosoft/PyRIT/.github/copilot-instructions.md
PyRIT (Python Risk Identification Tool for generative AI) is an open-source framework for security professionals to proactively identify risks in generative AI systems. ## Architecture PyRIT uses a modular pluggable
Model Context ProtocolCopilot instructionsmodelcontextprotocol/csharp-sdk/.github/copilot-instructions.md
package directories - Use `///` XML comments for all public APIs - Include ` ` sections for detailed explanations ## Security - Never commit secrets or API keys - Use environment variables for sensitive configuration - Support authentication mechanisms
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.
