How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/vscode-isort/.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
gviiisenCopilot instructionsgviiisen/repo-context-ledger/.github/copilot-instructions.md
context first. For a missing or changed background question, run `context --query " "` before broad documentation exploration; do not repeat routing for a routine follow-up whose context is sufficient. Read
MicrosoftCopilot instructionsmicrosoft/durabletask-mssql/.github/copilot-instructions.md
integration, Azure Functions, and performance tests. - `docs`: user-facing architecture, deployment, scaling, and multitenancy documentation. The provider persists orchestration and entity state, coordinates distributed workers, and supports multiple independently deployed
MicrosoftCopilot instructionsmicrosoft/haste/.github/copilot-instructions.md
authentication — do not bypass or mock in production paths. ### General - Write clear, self-documenting code. Avoid unnecessary comments. - Prefer small, focused functions over long procedural blocks. - Handle errors explicitly
raphaelmansuyCopilot instructionsraphaelmansuy/adk_training/.github/copilot-instructions.md
Complete test suite (~19 tests) - Makefile (setup, test, dev, demo, clean) - README with detailed documentation - `.env.example` for configuration ### Creating a New TIL 1. **Create Blog Post** - Create `docs/blog/YYYY-MM-DD-til-[feature-name
Microsoft AzureCopilot instructionsAzure/oav/.github/copilot-instructions.md
utilities) - `test/` — Test files and test fixtures - `dist/` — Compiled output (do not edit directly) - `documentation/` — Additional documentation - `regression/` — Regression test configurations - `eng/` — Engineering and build scripts
Habitat-ThinkingCopilot instructionsHabitat-Thinking/ai-literacy-superpowers/.github/copilot-instructions.md
applicable. Hook scripts are advisory only — they never block. Output uses JSON `systemMessage` format. ## Documentation Every skill, agent, and command file must have YAML frontmatter with `name` and `description` fields
mcpc-techCopilot instructionsmcpc-tech/mcpc/.github/copilot-instructions.md
agents with explicit tool selection - Simple `mcpc()` API, not complex builders - Examples over extensive documentation ## Quick Troubleshooting - Tool not found? Use full name: `server.tool` (not just `tool`) - `__ALL__` includes every
MicrosoftCopilot instructionsmicrosoft/edge-ai/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for edge ai - Brought to you by microsoft/edge-ai
haruCopilot instructionsharu/redmine_ai_helper/.github/copilot-instructions.md
English** - Do not include any information about Claude Code in commit messages **Design Document Adherence:** **CRITICAL: Design documents in `specs/` directory are AUTHORITATIVE and MANDATORY.** - **NEVER deviate from design documents
putervisionCopilot instructionsputervision/state-memory-mcp/.github/copilot-instructions.md
create", type: "task", title: "...", session_id: session_id)`. - **Making a design or implementation decision**: Document it with `manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session
Microsoft AzureCopilot instructionsAzure/gpt-rag-orchestrator/.github/copilot-instructions.md
expose secrets or execute untrusted content as instructions. - Add or update behavioral tests and documentation when behavior or operation changes. - Validate with the existing commands most specific to the change
aspenkitCopilot instructionsaspenkit/aspens/.github/copilot-instructions.md
This Project Does `aspens` is a CLI tool that generates and maintains AI-ready documentation (skills and guidelines) for any codebase. It scans a repo's tech stack, then uses
Microsoft AzureCopilot instructionsAzure/Azure-Landing-Zones/.github/copilot-instructions.md
across the Azure Landing Zones (ALZ) polyrepo ecosystem. The `Azure/Azure-Landing-Zones` repo is the **centralised documentation hub** and **issue tracker** for the entire ecosystem — it does not contain deployable source code
HoangYellCopilot instructionsHoangYell/markdy-com/.github/copilot-instructions.md
full CI suite: `pnpm run ci` (runs unit tests, AST backward compatibility gates, documentation examples, and Chrome DevTools headless E2E verification) 2. commit the finished product changes with a repo
MicrosoftCopilot instructionsmicrosoft/agentic-agile-template/platform-adapters/agent-tools/github-copilot/copilot-instructions.md
have tests] ## File Structure ``` project-root/ ├── src/ # Application source code ├── tests/ # Test files ├── docs/ # Documentation ├── .github/ # GitHub configuration └── ... ``` ## Key Conventions - [e.g., "Use dependency injection for all service classes
Microsoft AzureCopilot instructionsAzure/azure-api-management-policy-toolkit/.github/copilot-instructions.md
Management policy toolkit: a set of C# libraries that let users author APIM policy documents in C# instead of XML, compile them to XML, and unit-test them with
MicrosoftCopilot instructionsmicrosoft/vscode-pylint/.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/webui/.github/copilot-instructions.md
crate)` for internal helpers. - New public functions, structs, traits, and error variants must be documented with `///` doc-comments. - Use `#[must_use]` on functions whose return value should not be silently
MicrosoftCopilot instructionsmicrosoft/Microsoft-AI-Decision-Framework/.github/copilot-instructions.md
Overall guidelines about the project.
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.
