How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
OWASPCopilot instructionsOWASP/wrongsecrets/.github/copilot-instructions.md
OWASP WrongSecrets - Copilot Instructions Welcome to the OWASP WrongSecrets project! This document provides GitHub Copilot with essential context to help you contribute effectively to this educational cybersecurity project. ## Project Overview
Steady15 mentions in 2 weeks
No other project uses it yet
pnpCopilot instructionspnp/cli-microsoft365/.github/copilot-instructions.md
test file next to the command file. Create a reference page in the documentation in `docs/docs/cmd/ `. The reference page file name is the same as the command file name
TheSuperHackersCopilot instructionsTheSuperHackers/GeneralsGameCode/.github/copilot-instructions.md
compatibility - Use RTS_BUILD_OPTION_DEBUG=OFF for compatibility testing ## Development Workflow ### Code Change Documentation **Every user-facing change requires TheSuperHackers comment format:** ```cpp // TheSuperHackers @keyword author DD/MM/YYYY Description ``` Common
MicrosoftCopilot instructionsmicrosoft/pict/.github/copilot-instructions.md
code patterns and conventions 3. **Test**: Add comprehensive test cases with edge cases 4. **Document**: Update both code comments and user documentation 5. **Validate**: Test on multiple platforms and with
yohey-wPipes a download into a shellCopilot instructionsyohey-w/multi-agent-shogun/.github/copilot-instructions.md
GitHub Copilot CLI + tmux multi-agent parallel dev platform with sengoku military hierarchy
OfficeDevCopilot instructionsOfficeDev/Microsoft-Teams-Samples/.github/copilot-instructions.md
practices. --- ## Development Priority Guidelines ### 1. **Teams-First Approach** - Always reference Microsoft Teams samples and documentation first. - Prioritize Teams Platform APIs over generic Bot Framework patterns. - Use Teams-specific terminology
Gu1llaum-3Copilot instructionsGu1llaum-3/sshm/.github/copilot-instructions.md
m.cursor > 0 { m.cursor-- } case key.Matches(msg, keys.Down): if m.cursor < len(m.items)-1 { m.cursor++ } } ``` --- ## 16) Documentation & Comments * Exported types/functions must have a sentence GoDoc. * At the top of each file, include
nasirkhanCopilot instructionsnasirkhan/laravel-starter/.github/copilot-instructions.md
concise in your explanations - focus on what's important rather than explaining obvious details. ## Documentation Files - You must only create documentation files if explicitly requested by the user. === boost rules
se2pCopilot instructionsse2p/pynguin/.github/copilot-instructions.md
Project architecture and codebase structure - AI Agent Development Guidelines (code quality, testing, restrictions) - Module documentation and navigation - Code Quality standards, testing requirements, and restrictions If you read this file
justrachCopilot instructionsjustrach/codedb/.github/copilot-instructions.md
tests minimal — only exercise the specific broken code path ### Code Style - No comments or documentation changes unless explicitly asked - Prefer minimal, targeted fixes over refactors - Follow existing patterns
bitfoundationCopilot instructionsbitfoundation/bitplatform/.github/copilot-instructions.md
sample_search` tools of the `bitplatform` MCP server to search Microsoft's latest official documentation for detailed and up-to-date information before responding to specific or narrowly defined questions
HalFrgrdCopilot instructionsHalFrgrd/flyline/.github/copilot-instructions.md
Prefer `anyhow::Result` for fallible functions. - Keep `unsafe` blocks as small as possible and document why each one is necessary. - Do not introduce new dependencies without a clear justification; check
reatomCopilot instructionsreatom/reatom/.github/copilot-instructions.md
must add a test that reproduces the bug. - New features must be tested and documented. - Use `@ts-expect-error` for known false positives; `@ts-ignore` only for errors
tryzealotReads credentialsCopilot instructionstryzealot/zealot/.github/copilot-instructions.md
boot smoke; there is no test suite. `spec/api/*` is an rswag OpenAPI **document generator**: rswag drives it in dry-run (`.rspec` sets `--dry-run`), so `run_test!` never issues
piratuksReads credentialsCopilot instructionspiratuks/invoice-builder/.github/copilot-instructions.md
apps/server/main.ts` (dev: `npm run dev:webserver`, build: `npm run build:webserver` -> `dist-server/main.js`) - Documentation website: `apps/website` (Docusaurus, renders `docs/` content; dev: `npm run dev:website`, build: `npm run build
Steady3 mentions in 2 weeks
No other project uses it yet
MicrosoftDocsCopilot instructionsMicrosoftDocs/sql-docs/.github/copilot-instructions.md
These instructions define a unified style and process standard for authoring and maintaining learn.microsoft.com documentation with GitHub Copilot or other AI assistance. ## Learn-wide Instructions Below are instructions that apply
PropertyToolsCopilot instructionsPropertyTools/PropertyTools/.github/copilot-instructions.md
SelectedColor`, `UndefinedColor`) - **Parameters and Local Variables** - Use camelCase (e.g., `color`, `alpha`, `targetType`) 4. **XML Documentation** - Use XML documentation comments (`///`) for public APIs - Include ` `, ` `, and ` ` tags as appropriate - Example: ```csharp /// /// Change
datalayerCopilot instructionsdatalayer/jupyter-mcp-server/.github/copilot-instructions.md
uses a modern Python build system with hatch, and includes comprehensive testing, linting, and documentation. ## Working Effectively ### Environment Setup - **Python Requirements**: Python 3.10 or higher (tested with 3.9-3.13) - **Network
No other project uses it yet
SupabaseCopilot instructionssupabase/supabase-swift/.github/copilot-instructions.md
supabase-swift ## Instructions for Code Review - Check for breaking API changes - Check if documentation is up to date - Check if examples are up to date - Check if tests are comprehensive
Steady8 mentions in 2 weeks
No other project uses it yet
mozillazgCopilot instructionsmozillazg/ptcpdump/.github/copilot-instructions.md
test` to validate 5. Add E2E test script in `testdata/` if needed 6. Update documentation in README.md if user-facing ### Fixing a Bug 1. Reproduce the issue
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.
