How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
andreaswasitaCopilot instructionsandreaswasita/copilot-agents-dojo/.github/copilot-instructions.md
verify each 5. **[Test writing](../skills/test-writing/SKILL.md)** → RED-GREEN-REFACTOR for every change 6. **[Requesting code review](../skills/requesting-code-review/SKILL.md)** → Self-review against plan 7. **[Finishing a development branch](../skills/finishing-a-development-branch/SKILL.md)** → Verify, merge decision
MicrosoftCopilot instructionsmicrosoft/Trieste/.github/copilot-instructions.md
begin step N+1 until step N is fully complete: code written, compiled, tests passing, and reviewed. - **No skipping.** Even if a later step seems independent, execute
nubbymongCopilot instructionsnubbymong/claude-command-center/.github/copilot-instructions.md
files via `src/main/config-manager.ts` - Stores are in `src/renderer/stores/` using Zustand - hydrated from config on startup ## Coding Style - Use named exports. Default exports only for React components that are the sole export
WYRE-AICopilot instructionsWYRE-AI/autotask-mcp/.github/copilot-instructions.md
Copilot Code Review Instructions — MCP Server Template > This file applies to all WYRE MCP servers (autotask-mcp, datto-rmm-mcp, syncro-mcp, halopsa-mcp, ninjaone-mcp, liongard-mcp, connectwise-manage
Microsoft AzureCopilot instructionsAzure/kafka-sink-azure-kusto/.github/copilot-instructions.md
Automated Code Review — kafka-sink-azure-kusto You are the **Principal Reviewer** for this repository: an autonomous, elite **Principal Software Engineer and Distributed Systems Architect** specializing in Java, Kafka Connect
FmarzochiCopilot instructionsFmarzochi/EGC/.github/copilot-instructions.md
below it (sponsors, backers, OpenSSF footer) changes only when the maintainer edits it deliberately. ## Code review priorities - Commits need a DCO Signed-off-by line and follow conventional commits
MicrosoftCopilot instructionsmicrosoft/moc/.github/copilot-instructions.md
errors (format code and run tests) - ✅ No compilation errors or warnings that would block the build ### How to Verify Status Before marking a PR as ready for review, use GitHub
MicrosoftCopilot instructionsmicrosoft/vscode-flake8/.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
ariffazilCopilot instructionsariffazil/arifOS/.github/copilot-instructions.md
dodge an `ANONYMOUS` → `SOVEREIGN` gate. - Manually compute a floor metric in ad-hoc code and skip the kernel call. The kernel is the only authorized scorer. ### 5. Vault Rule — write
AnalyticAceCopilot instructionsAnalyticAce/binance-mcp-server/.github/copilot-instructions.md
auto-generated + manual) - Implement change logs - Use diagrams for complex systems (C4 model recommended) ### Code Review Process - Establish code review checklist - Use pull requests for all changes - Enforce style guidelines
PinkR1verCopilot instructionsPinkR1ver/vibe-roast/.github/copilot-instructions.md
public path contract. - Preserve English and Chinese behavior for product copy and generated output. Review requirements: - Give the file and smallest useful line range. - Provide a concrete failing input
TrifallCopilot instructionsTrifall/chat-export/.github/copilot-instructions.md
adding new features or modifying existing ones, review the current project state - Consider previously discussed or implemented features to prevent contradictions ## Code Output Guidelines - Provide complete file content, not just
MicrosoftCopilot instructionsmicrosoft/rego-cpp/.github/copilot-instructions.md
defined inline alongside the pass logic. **Always read the well-formedness definition before writing code that traverses the AST** — nodes are wrapped (e.g., Array elements live inside Term nodes
vaquarkhanCopilot instructionsvaquarkhan/data-engineering-agent-skills/.github/copilot-instructions.md
workflow skills from `skills/` 5. Use checklist references from `references/` for review and verification ## Behavior - prefer specification before code changes - keep contracts, grain, and ownership explicit - do not treat
drvossCopilot instructionsdrvoss/everything-copilot-cli/COPILOT-INSTRUCTIONS.md
line description of what this agent does agent_type: general-purpose | explore | task | code-review model: claude-sonnet-4.6 | gpt-5-mini | claude-haiku-4.5 tools: - grep - glob - view - edit
drvossCopilot instructionsdrvoss/everything-copilot-cli/.github/copilot-instructions.md
purpose` | "Add a new agent with skills and tests", "Refactor rule structure" | | Reviewing changes | `code-review` | "Review this PR", "Check for issues in staged changes" | | Parallel independent work | Fleet mode
Naridon-IncCopilot instructionsNaridon-Inc/aura/.github/copilot-instructions.md
Multi-file feature | `aura plan "objective"` → `aura execute` | | Before commit | `aura log-intent "why"` | | Code review | `aura pr-review --base main` | | Verify behavior | `aura goal-trace "goal"` | | Fix broke something
bug-opsCopilot instructionsbug-ops/mcp-execution/.github/copilot-instructions.md
Execution project, synthesizing expertise from architectural design, development practices, testing strategies, performance optimization, security, code review, and CI/CD. --- ## Table of Contents 1. [Project Context](#project-context) 2. [Core Principles](#core
oak-investCopilot instructionsoak-invest/kiso/.github/copilot-instructions.md
source remains structured Markdown, the knowledge base stays readable, versionable with Git, easy to review, and usable by AI agents. Kiso sits between two needs: simple text files for maintaining
nitinjain999Copilot instructionsnitinjain999/platform-skills/.github/copilot-instructions.md
where Kubernetes, GitOps, CI/CD, and security concerns intersect. Apply these patterns when generating or reviewing code across Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions (composite actions, OIDC, SHA pinning
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.
