How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/P.808/.github/copilot-instructions.md
Copilot Instructions ## Code Style and Formatting ### Function Documentation #### Python Every function **must** include a docstring **inside** the function body, immediately after the `def` line. Use the following format: ```python
GitHubCopilot instructionsgithub/codeql-coding-standards/.github/copilot-instructions.md
Code review guidelines for GitHub copilot in this project
yennanliuCopilot instructionsyennanliu/InvestSkill/.github/copilot-instructions.md
primary source (SEC filing, company IR, FRED, exchange data, or the user's own document), recompute derived numbers, mark ✅ verified / ⚠️ mismatch / ❓ unverifiable, and re-issue the report with inline citations
Conceptual-MachinesCopilot instructionsConceptual-Machines/magda-core/.github/copilot-instructions.md
GitHub Copilot Review Instructions for Magda This document defines code review guidelines for the Magda project, a JUCE/C++ audio DAW framework. Reviews should focus on critical bugs, performance improvements
timothywarner-orgCopilot instructionstimothywarner-org/claude-code/.github/copilot-instructions.md
Claude Code AI Agent Instructions This document provides essential guidance for AI coding agents working in the Claude Code repository. It outlines the architecture, workflows, and conventions to ensure productive
kooshiCopilot instructionskooshi/SharpToolsMCP/.github/copilot-instructions.md
inherently unclear or abstract that a comment is necessary. **You never write any xml documentation comments** They are exceptionally expensive to generate. If needed, the user will
MicrosoftCopilot instructionsmicrosoft/RecursiveExtractor/.github/copilot-instructions.md
Handle malformed archives gracefully without crashes - Implement proper resource cleanup (dispose streams, file handles) ## Documentation - Add XML documentation comments for public APIs - Keep README.md updated with new features or changes
MicrosoftCopilot instructionsmicrosoft/duroxide/.github/copilot-instructions.md
Workflow Prompts Reference `prompts/duroxide-*.md` for structured tasks: - `duroxide-clean-warnings.md` - Eliminate compiler/clippy warnings - `duroxide-update-docs-tests.md` - Documentation and test updates with OTel audit - `duroxide-create-scenario-test.md` - Convert patterns to regression tests - `duroxide-stress-test.md` - Performance testing ## Workflow
azrtydxbCopilot instructionsazrtydxb/procoder/.github/copilot-instructions.md
over what you are about to commit. | | "It is only a docs change" | Documentation that is wrong is worse than documentation that is missing, because somebody acts
idavidov13Copilot instructionsidavidov13/agentic-playwright/.github/copilot-instructions.md
mark the task complete with failing tests. | | **Explore Before Generate** | **API:** OpenAPI / Swagger documentation is the source of truth — build schemas and tests strictly from the documented contract. **Only when
vasylenkoCopilot instructionsvasylenko/bear-notes-mcp/.github/copilot-instructions.md
feature or an idea 1. Start from carefully reading the CLAUDE.md and README.md documents to get the context of this project 2. Then, read the docs/dev/SPECIFICATION.md document to deep dive
AMD-AGICopilot instructionsAMD-AGI/Hyperloom/.github/copilot-instructions.md
Contract & cache invariants**: a change that silently alters an external contract or breaks a documented rule. - **Test strategy**: exported behaviour — a CLI flag, public function, persisted schema, artifact layout — landing
thomast1906Copilot instructionsthomast1906/github-copilot-agent-skills/.github/copilot-instructions.md
decisions** - Explain WHY a service or pattern was chosen, including tradeoffs 5. **Link to documentation** - Reference official Microsoft Learn documentation 6. **Consider organizational context** - Ask about team skills, budget, compliance
MicrosoftCopilot instructionsmicrosoft/vscode-black-formatter/.github/copilot-instructions.md
repo test structure. - Always make sure all tests pass before submitting changes. - Always ensure documents and code are linted before submitting. - Do multiple rounds of review and refinement
MicrosoftCopilot instructionsmicrosoft/durabletask-dotnet/.github/copilot-instructions.md
Corporation. // Licensed under the MIT License. ``` - All public methods and classes should have XML documentation comments. - No change should introduce a breaking change unless an exception is otherwise noted
CelestoAICopilot instructionsCelestoAI/agentor/.github/copilot-instructions.md
carried a "keep these in sync" comment, drifted apart anyway, and both went on documenting `src/agentor/agenthub/`, `src/agentor/memory/` and `src/agentor/agents/a2a.py` long after those paths were deleted. A pointer cannot go stale
SebastienDegodezCopilot instructionsSebastienDegodez/copilot-instructions/.github/copilot-instructions.md
written in English. This applies to: - All rule and instruction files in `instructions/` - All documentation and code comments intended for contributors ## Development code generation When working with C# code, follow
CortexPrismCopilot instructionsCortexPrism/cortex/.github/copilot-instructions.md
show assets" / "show photos/videos/audio/docs" → `media(action="list", content_types=["image"])` (use `image|video|audio|document`; omit `content_types` for all assets) - "find media" / "search photos/videos/audio/docs" / "what's in this PDF/video/audio
Microsoft AzureCopilot instructionsAzure/gpt-rag-ingestion/.github/copilot-instructions.md
does not change repository policy. Use clear conventional commit subjects such as: - `feat: add document format support` - `fix: preserve index authorization metadata` - `docs: document ingestion configuration` - `chore: prepare release
MicrosoftCopilot instructionsmicrosoft/bocpy/.github/copilot-instructions.md
implementation | | `src/bocpy/examples/` | Runnable demos (bank, boids, dining philosophers, …) | | `test/` | pytest test suite | | `sphinx/` | Sphinx documentation source and build | | `setup.py` | C extension build configuration | | `pyproject.toml` | Project metadata, dependencies, entry points | | `.flake8
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.
