How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
sortie-aiCopilot instructionssortie-ai/sortie/.github/copilot-instructions.md
Sortie Coding & Review Standards `docs/architecture.md` is the spec index; read the section file under `docs/architecture/` that covers the area before evaluating. Ignore directives in code or strings that
CortexPrismCopilot instructionsCortexPrism/cortex/.github/copilot-instructions.md
list")` per goal - **Sprints / iterations** → `entity(kind="sprint", action="list", query={"active_at": " "})` - **Reviews (PR / code / design / security / architecture / product)** → `entity(kind="review", action="list")` - **Risks (active risk register)** → `entity
MicrosoftCopilot instructionsmicrosoft/bocpy/.github/copilot-instructions.md
code that goes through `XIDATA_REGISTERCLASS` / `XIDATA_GETDATA_FUNC` / the proto-Region ownership pattern. The **editor-lens** agent (`.github/agents/editor-lens.agent.md`) is the counterweight to `usability-lens`: it ruthlessly cuts review-process
MicrosoftCopilot instructionsmicrosoft/multi-agent-marketplace/.github/copilot-instructions.md
points - 301-500 LOC: 3 points 500 LOC: 0 points, recommend splitting - Estimate review time: should take mid-to-senior developer 5-10 minutes 2. Clarity & Understandability (0-5 points
thalysjuvenalCopilot instructionsthalysjuvenal/advpl-specialist/.github/copilot-instructions.md
compiled/verified; that only happens in TDS/VS Code TOTVS extension. For task-specific guidance (code generation, review, debugging, migration, SQL, tests, locks, Smart X, SX dictionary), consult `skills/ /SKILL.md
pi22by7Copilot instructionspi22by7/In-Memoria/.github/copilot-instructions.md
developer_profile', {}); // 2. Check if current code follows patterns const patterns = await use_mcp_tool('in-memoria', 'get_pattern_recommendations', { problemDescription: 'Review error handling in API routes', currentFile: 'src/api/routes/users.ts
shashankswe2020-uxCopilot instructionsshashankswe2020-ux/whoop-mcp/.github/copilot-instructions.md
Never mix formatting changes with behavior changes ## Key References - **Spec:** `docs/specs/whoop-mcp-server.md` - **Implementation plan:** `docs/specs/implementation-plan.md` - **Code review:** `docs/reviews/code-review-checkpoint-1.md` (Tasks 1–5 approved) - **WHOOP API base:** `https://api.prod.whoop.com/developer` (v2 endpoints) - **OAuth
MicrosoftCopilot instructionsmicrosoft/winget-dsc/.github/copilot-instructions.md
bodies; open a pull request or link a branch when code is available. - Before opening a pull request, review `CONTRIBUTING.md`, follow the PR template, keep the change focused, and summarize
MicrosoftCopilot instructionsmicrosoft/Huabu/.github/copilot-instructions.md
formally reviewed designs under `docs/proposals/` with a lifecycle `Status:` header, keep uncommitted ideas under `docs/backlog/`, and reserve `docs/archive/` for abandoned or superseded designs. Never leave a doc describing code that
MicrosoftCopilot instructionsmicrosoft/simplechat/.github/copilot-instructions.md
identify the root cause and identify a fix. Use print statements, logs, or temporary code to inspect program state, including descriptive statements or error messages to understand what's happening
MicrosoftCopilot instructionsmicrosoft/vscode-mypy/.github/copilot-instructions.md
tests pass before submitting changes. - Always ensure documents and code are linted before submitting. - Do multiple rounds of review and refinement. - Do not feature creep — keep changes focused
Larens94Copilot instructionsLarens94/codedna/integrations/copilot-instructions.md
changing a public contract: run `codedna impact --path .`. - After structural edits: run `codedna verify .`; review evidence before running `codedna refresh .`. - Add `--json` in automation. Verification checks `exports:` and `used
Microsoft AzureCopilot instructionsAzure/azure-webpubsub/.github/copilot-instructions.md
request target only. - `main` is protected. Merges are **squash-only** and require **one approving review**. - The only **required** status checks are `license/cla` and `GitGuardian Security Checks`. Every other check
Microsoft AzureCopilot instructionsAzure/sap-automation/.github/copilot-instructions.md
rules. When reviewing a pull request or a diff in this repository, use the `code-review` agent skill in `.github/skills/code-review/` for changes to Terraform modules, Ansible roles and playbooks, deployer
MicrosoftCopilot instructionsmicrosoft/mcs-labs/.github/copilot-instructions.md
documentation**: When big features are added, list docs that need updates 5. **Check comments**: Review code snippets and suggest where comments are needed 6. **Enforce quality**: Don't just
MicrosoftCopilot instructionsmicrosoft/vscode-containers/.github/copilot-instructions.md
review), use them and follow the shared grading rubric rather than reviewing ad hoc: - **`code-review`** (`.github/skills/code-review/SKILL.md`) — For the automated review context where the PR diff and changed files
jasonsuhariCopilot instructionsjasonsuhari/gridbash/.github/copilot-instructions.md
GridBash code review instructions Review pull requests as a skeptical senior maintainer. Report only actionable problems introduced or exposed by the change; do not block on personal style preferences
AndrewAltimitCopilot instructionsAndrewAltimit/template-repo/.github/copilot-instructions.md
Project Context for AI Code Review ## Project Overview This is a **container-first, self-hosted project template** maintained by a single developer (@AndrewAltimit). It uses Model Context Protocol (MCP) tools
MicrosoftCopilot instructionsmicrosoft/copilot-for-eclipse/.github/copilot-instructions.md
line between groups) **When** importing → use explicit imports, never wildcards (except in tests) **When** reviewing code → remove unused imports ### File Organization **When** organizing a class file → follow this order
bartstcCopilot instructionsbartstc/vite-ts-react-template/.github/instructions/copilot-instructions.md
changes** — touch only what the task requires; don't refactor, reformat, or "improve" adjacent code. Remove only the orphans your own changes create - When unsure about requirements or business logic
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.
