How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
ivuorinenCopilot instructionsivuorinen/skills/.github/copilot-instructions.md
duplicate it here. Nitpicker in one line: adversarial, exhaustive auditing across code, security, tests, docs, architecture, performance, dependencies, error handling, CI, commits, migrations, observability, contracts, a11y, privacy, config, leaks, i18n
jonathan-vellaCopilot instructionsjonathan-vella/bmit-2026/.github/copilot-instructions.md
migrate` | Cross-cloud migration assessment and code conversion to Azure | | `azure-compliance` | Compliance scanning, security auditing, Key Vault expiration monitoring | | `azure-compute` | VM size recommendations, VMSS, configuration guidance | | `azure-cost
juwonllee2024-dotcomCopilot instructionsjuwonllee2024-dotcom/rulesync/.github/copilot-instructions.md
Jest. - Maintain high test coverage and test edge cases and error paths explicitly. ### Security & Privacy Guidelines - Never hardcode API keys, access tokens, or secrets in source code. - Always validate external
LuxvilCopilot instructionsLuxvil/ai-coding-rules/copilot-instructions.md
PATCH (diffs with paths) - VERIFICATION (commands + manual checks) - NOTES (tradeoffs/risks) --- ## Stop Triggers - Security implication - Data loss - Breaking change - >3 files or >200 LOC without approval --- ## References - MASTER_RULES.md - global_rules.md - security_privacy.md - project_profile.md
MCLifeLeaderCopilot instructionsMCLifeLeader/seq-mcp/.github/copilot-instructions.md
access to Datalust Seq OpenTelemetry data. ## Priority Rules 1. Follow `.github/instructions/seq-mcp-server.instructions.md` first. 2. Apply security guidance from `.github/instructions/security-and-owasp.instructions.md`. 3. Apply container guidance from `.github/instructions/containerization-docker-best-practices.instructions.md`. If rules conflict, the more specific
rios0rios0Copilot instructionsrios0rios0/guide/.github/copilot-instructions.md
Version control workflows │ ├── Documentation-&-Change-Control/ # Templates and change control │ └── *.md # Tests, CI-&-CD, Security, Git-Flow, Architecture ├── Code-Style/ # Language-specific coding guidelines │ ├── GoLang/ # Go: conventions, formatting, types, logging
soderlindCopilot instructionssoderlind/skills/skills/wp-prepare/references/copilot-instructions.md
This phase adds a project-scoped Copilot instructions file so agents follow WordPress coding, security, i18n, performance, and testing best practices. Source: [github/awesome-copilot](https://github.com/github/awesome-copilot/blob/main/instructions/wordpress.instructions.md) (MIT License). Prefer downloading
spantailCopilot instructionsspantail/spantail/.github/copilot-instructions.md
split one concern into many separate line comments. - Prioritize what matters: correctness, security, permission scoping, and violations of the architecture invariants in `docs/conventions.md`. Lead with these. ## What to avoid
stdinCopilot instructionsstdin/buy-vs-build/.github/copilot-instructions.md
commercial dependency, research it — maintenance and health (active maintainers, release cadence, adoption, bus factor), security and supply chain (known vulnerabilities, install scripts, provenance), license, and transitive footprint — and prefer
u9401066Copilot instructionsu9401066/template-is-all-you-need/.github/copilot-instructions.md
review, 審查, 檢查, PR | | **test-generator** | 測試生成 + 靜態分析 | TG, test, 測試, coverage, pytest | | **security-reviewer** | 安全性審查 (OWASP) | SEC, security, 安全, OWASP, 漏洞 | ### 記憶管理 | Skill | 用途 | 觸發詞 | |-------|------|--------| | **memory-updater** | Memory Bank
vzubcuCopilot instructionsvzubcu/dotnet-48-master-architect-skill/.github/copilot-instructions.md
Coverage targets: New code >80%, legacy after refactor >60% - Test ViewModels/Presenters, never Views/Forms directly ## Security - ServicePointManager.SecurityProtocol = Tls12 - Parameterized queries / EF6 only — zero SQL string concatenation - AntiForgeryToken on all state-changing
zircote-pluginsCopilot instructionszircote-plugins/agents/.github/copilot-instructions.md
agents/ # 115+ specialized agents 01-core-development/ 02-language-specialists/ 03-infrastructure/ 04-quality-security/ 05-data-ai/ 06-developer-experience/ 07-specialized-domains/ 08-business-product/ 09-meta-orchestration
26zlCopilot instructions26zl/universal-agent-skills/.github/copilot-instructions.md
Prefer self-explanatory code. - Add comments only for non-obvious intent, invariants, constraints, workarounds, security boundaries, or surprising tradeoffs. - Keep comments factual, neutral, and normally one sentence. - Never mention prompts
almirjameeCopilot instructionsalmirjamee/copilot-config/copilot-instructions.md
category, note To view recent audit entries: ```bash tail -20 ~/.copilot/logs/audit.jsonl | jq . # or view security blocks only: jq 'select(.decision=="BLOCK")' ~/.copilot/logs/audit.jsonl | tail -10 ``` ### Agents must self-assess blast radius
ancyonioCopilot instructionsancyonio/OracleDBIQ/.github/copilot-instructions.md
Copilot Instructions The full Oracle PL/SQL development, optimization, security and diagnostics standards for this repository live in **[AGENTS.md](../AGENTS.md)** — the single source of truth, read natively by both GitHub Copilot
AnselmooCopilot instructionsAnselmoo/mcp-zen-of-languages/.github/copilot-instructions.md
import SubprocessToolRunner runner = SubprocessToolRunner() if runner.is_available("shellcheck"): result = runner.run("shellcheck", ["-"], code=script_code) ``` - Security: allowlist of known tools (`KNOWN_TOOLS` mapping), no `shell=True` - Supported tools are language-scoped
AraszCopilot instructionsArasz/ai-badger/.ai-badger/copilot-instructions.md
auditing whether an existing test can actually fail → `test-engineer` - Quality gate before merge, security review, and adversarially verifying a claim this session made about its own work → `code-reviewer
AraszCopilot instructionsArasz/ai-badger/.github/copilot-instructions.md
auditing whether an existing test can actually fail → `test-engineer` - Quality gate before merge, security review, and adversarially verifying a claim this session made about its own work → `code-reviewer
AraszCopilot instructionsArasz/ai-raccoon/.ai-badger/copilot-instructions.md
lock and rewrites only the key it was given. → `.ai-badger/invariants/never-hand-edit-the-git-dir.md` - **Use platform security APIs** — Always use the platform's built-in security and crypto APIs. → `.ai-badger/invariants/no-hand-rolled-crypto.md
AraszCopilot instructionsArasz/ai-raccoon/.github/copilot-instructions.md
lock and rewrites only the key it was given. → `.ai-badger/invariants/never-hand-edit-the-git-dir.md` - **Use platform security APIs** — Always use the platform's built-in security and crypto APIs. → `.ai-badger/invariants/no-hand-rolled-crypto.md
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.
