How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
kooshiCopilot instructionskooshi/SharpToolsMCP/.github/copilot-instructions.md
Data Structures, Design patterns, Functional programming, Parallel programming You focus on elegance, maintainability, readability, security, "clean code", and best practices. You always write the minimum amount of code to accomplish
MicrosoftCopilot instructionsmicrosoft/RecursiveExtractor/.github/copilot-instructions.md
test data directories - Include edge cases: nested archives, encrypted files, malformed content, zip bombs ## Security Considerations - The library includes protections against ZipSlip, Quines, and Zip Bombs - Always validate file paths
jonathan-vellaCopilot instructionsjonathan-vella/apex/.github/copilot-instructions.md
required contract — `ManagedBy` may > still be emitted as an optional deploy-provenance marker. ### Security baseline + AVM mandate Non-negotiable: HTTPS-only, TLS 1.2 minimum, no public blob, Managed Identity over
azrtydxbCopilot instructionsazrtydxb/procoder/.github/copilot-instructions.md
caller before editing. Never simplify away input validation, error handling that prevents data loss, security, or accessibility. Non-trivial logic leaves one runnable check behind. A repo overrides these wholesale
FerroxLabsCopilot instructionsFerroxLabs/ijfw/copilot/copilot-instructions.md
bullets. explain/teach -- only when user says "why" or "explain". Use normal English for: security warnings, destructive actions, user confusion, multi-step sequences. Resume terse after. ## Memory routing Session start: call
MicrosoftCopilot instructionsmicrosoft/MicroHack/03-Azure/01-04-AI/01_Agentic_SDLC/.github/copilot-instructions.md
generating suggestions: 1. Prefer incremental, minimal diffs; preserve existing style and naming. 2. Surface security, correctness, and data integrity issues before micro-optimizations. 3. Encourage type safety (no `any` unless
KbWenCopilot instructionsKbWen/agentic-os/.github/copilot-instructions.md
review priorities. - Prefer focused, file/line-specific findings over broad style suggestions. - Treat correctness, security, missing tests, governance-bypass, and stale spec/backlog/SSoT metadata as higher priority than formatting. - Do not duplicate
thomast1906Copilot instructionsthomast1906/github-copilot-agent-skills/.github/copilot-instructions.md
Balance all five pillars** - Consider Cost Optimization, Operational Excellence, Performance Efficiency, Reliability, and Security together 4. **Justify decisions** - Explain WHY a service or pattern was chosen, including tradeoffs 5. **Link
sortie-aiCopilot instructionssortie-ai/sortie/.github/copilot-instructions.md
termination condition. No pointer capture in closures without snapshot/sync. ## 3. Workspace path safety (critical: security boundary) - Containment of workspace paths under `workspace.root` after absolute normalization; no escape symlinks. - Issue identifiers
CortexPrismCopilot instructionsCortexPrism/cortex/.github/copilot-instructions.md
review" / "design review" → `entity(kind="review", action="create", body={"title": "...", "kind": "pr|code|design|security|architecture|product", "subject_ref": "github:org/repo#123", "reviewer_ids": [...]})` - "list reviews" / "pending reviews" → `entity(kind
ECPayCopilot instructionsECPay/ECPay-API-Skill/.github/copilot-instructions.md
files, **always run `bash scripts/validate-ai-index.sh`** to confirm line numbers still point to correct headings. ### Security-Critical: Timing-Safe Comparison All crypto verification code **must** use timing-safe comparison functions. Never
Azure-SamplesCopilot instructionsAzure-Samples/eShopLite/copilot-instructions.md
Azure AI integrations (Azure OpenAI, Azure AI Search, etc.), follow official SDK and security guidelines 7. Use configuration via `appsettings.json` and dependency injection for new .NET code 8. Keep code
shashankswe2020-uxCopilot instructionsshashankswe2020-ux/whoop-mcp/.github/copilot-instructions.md
test` after every change ## Code Quality - Review across five axes: correctness, readability, architecture, security, performance - Every PR must pass: lint, type check, tests, build - No secrets in code or version
shunk031Copilot instructionsshunk031/dotfiles/.github/copilot-instructions.md
Commit messages: Follow the `Commit messages` rule in `AGENTS.md` (Conventional Commits, ` ( ): `, lowercase imperative summary). - Security: Never suggest or commit secrets, API keys, or other personal data. Private dotfiles are managed
MohamedAbdallah-14Copilot instructionsMohamedAbdallah-14/unslop/.github/copilot-instructions.md
anti-detector Stop: "stop unslop" or "normal mode" Auto-Clarity: drop unslop style for security warnings, irreversible actions, legal/medical/financial precision, user confused. Resume after. Boundaries: code/commits/PRs written normal. Never invent
AiTerminalFoundationCopilot instructionsAiTerminalFoundation/ai-terminal/.github/copilot-instructions.md
primary targets) - **AI integration** is a core feature - be mindful of Ollama API calls - **Security**: Handle shell command execution carefully to prevent injection - **Performance**: Keep the UI responsive; use async
forefyCopilot instructionsforefy/.context/.github/copilot-instructions.md
This repo contains instruction files for using and conducting security reviews, do not confuse this `copilot-instructions.md` from other copilot-instructions files existing in this workspace. For every change
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/containerization/copilot-instructions.md
tasks and avoid manual interventions. - Write modular, reusable CI/CD pipelines. - Use containerized applications with secure registries. - Manage secrets using Azure Key Vault or other secret management solutions. - Build resilient systems
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/dotnet/copilot-instructions.md
MSTest. - Use Moq or NSubstitute for mocking dependencies. - Implement integration tests for API endpoints. ## Security - Use Authentication and Authorization middleware. - Implement JWT authentication for stateless API authentication. - Use HTTPS
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/java/copilot-instructions.md
processing with @Async for non-blocking operations. - Implement proper database indexing and query optimization. ## Security - Implement Spring Security for authentication and authorization. - Use proper password encoding (e.g., BCrypt). - Implement CORS
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.
