How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
relaticleCopilot instructionsrelaticle/relaticle/.github/copilot-instructions.md
Relaticle Code Review Guidelines ## Repository Context Multi-tenant SaaS CRM with paying customers. Tenant isolation is the highest-priority concern. A single cross-tenant data leak is a critical security
AvdLeeCopilot instructionsAvdLee/Swift-Concurrency-Agent-Skill/.github/copilot-instructions.md
GitHub Copilot Instructions: Agent Skills Expert Review code changes as an **Agent Skills expert**, focusing on the [Agent Skills open format](https://agentskills.io/home) specification and best practices. ## Core Agent
feiskyerCopilot instructionsfeiskyer/claude-code-settings/.github/copilot-instructions.md
Copilot when working with code in this repository. ## Environment Setup This repository contains Claude Code settings, configurations and guidance. The default setup uses GitHub Copilot as the model provider through
GitHubCopilot instructionsgithub/codeql-action/.github/copilot-instructions.md
directory. A GitHub Actions workflow checks that the JavaScript code in `lib` is up-to-date. Therefore, you should not review any changes to the contents of the `lib` folder
MongoDBCopilot instructionsmongodb/mongo-php-library/.github/copilot-instructions.md
GitHub Copilot Instructions ## Code Review Guidelines ### Review Focus - **Do not repeat or paraphrase the PR description** - Only highlight changes or notable information that was omitted from the description - Focus
MicrosoftCopilot instructionsmicrosoft/ai-dev-gallery/.github/copilot-instructions.md
InferenceSession` and other resources - Check for memory leaks in image processing code ### Sample Implementation Standards When reviewing PRs that add or modify samples: 1. **Class Structure** - Must inherit from `BaseSamplePage
MicrosoftCopilot instructionsmicrosoft/hve-core/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for hve-core
yigitkonurCopilot instructionsyigitkonur/cli-continues/.github/copilot-instructions.md
continues — Code Review Standards ## Read-Only Semantics - Session data is NEVER modified. Any PR that writes to `~/.claude/`, `~/.codex/`, `~/.copilot/`, `~/.gemini/`, `~/.factory/`, `~/.cursor/`, or `~/.local/share/opencode/` is a critical bug. - Handoff
yohey-wCopilot instructionsyohey-w/multi-agent-shogun/.github/copilot-instructions.md
GitHub Copilot CLI + tmux multi-agent parallel dev platform with sengoku military hierarchy
specstoryaiCopilot instructionsspecstoryai/getspecstory/.github/copilot-instructions.md
Ignore any changes to: - .specstory/history files - .claude files - ./specstory binary - CLAUDE.md - AGENT.md - changelog.md Please code review the pull request. Review line by line, pay attention to: - clarity of variable names
MicrosoftCopilot instructionsmicrosoft/waza/.github/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
MicrosoftCopilot instructionsmicrosoft/waza/.squad/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
MicrosoftCopilot instructionsmicrosoft/waza/.squad/templates/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
SupabaseCopilot instructionssupabase/supabase-swift/.github/copilot-instructions.md
Copilot Instructions for 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
MicrosoftCopilot instructionsmicrosoft/CSS-Exchange/.github/copilot-instructions.md
push, or create PRs without explicit user instruction. NEVER auto-fix issues found during code review. Report findings only. NEVER present code as complete without running `Invoke-CodeFormatterOnFiles` and `SpellCheck.ps1
MicrosoftCopilot instructionsmicrosoft/prompty/.github/copilot-instructions.md
# Prompty v2 — Complete Rebuild Plan ## Overview Prompty is being rebuilt from the ground up
MicrosoftCopilot instructionsmicrosoft/mssql-jdbc/.github/copilot-instructions.md
reproduce it and identify the root cause in source code. - If the issue is a feature request, review the proposal and assess its feasibility. - If the issue is a task
MicrosoftCopilot instructionsmicrosoft/onnxruntime-genai/.github/copilot-instructions.md
models ..\models # C++ unit tests via CMake/CTest ctest --build-config Release --output-on-failure ``` ## Code Patterns & Conventions ### Device Interface Pattern Each hardware backend implements `DeviceInterface` (defined in `src/smartptrs.h`): ```cpp struct
openops-cloudCopilot instructionsopenops-cloud/openops/.github/copilot-instructions.md
following instructions are only to be applied when performing a code review. # Pull Request Review Guidelines Review the current pull request diff for security, code quality/readability, performance, test coverage
MicrosoftCopilot instructionsmicrosoft/testfx/.github/copilot-instructions.md
accessors. - IMPORTANT: Make sure to apply this rule strictly both during PR review and when working on code changes. - Every API marked with `[Experimental]` MUST include this sentence
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.
