How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
affaan-mCopilot instructionsaffaan-m/ECC/.github/copilot-instructions.md
Full diff reviewed (`git diff [base-branch]...HEAD`) - Test plan included in PR description - Code review is handled by CodeRabbit and Greptile. Do not add or route PR code review
MicrosoftCopilot instructionsmicrosoft/vscode/extensions/copilot/.github/copilot-instructions.md
flows - **`survey/`**: User feedback and survey collection **Specialized Features:** - **`notebook/`**: Notebook integration and support - **`review/`**: Code review and PR integration features - **`renameSuggestions/`**: AI-powered rename suggestions - **`ignore/`**: File and pattern
MicrosoftCopilot instructionsmicrosoft/vscode/.github/copilot-instructions.md
valid-layers-check` only when a change may affect module layering. ## Coding Guidelines ### Indentation We use tabs, not spaces. ### Naming Conventions - Use PascalCase for `type` names - Use PascalCase for `enum
MicrosoftCopilot instructionsmicrosoft/TypeScript/.github/copilot-instructions.md
ideal to implement features and fixes in the following order, and commit code after each step: 1. Write a minimal test case, or test cases, that demonstrate
SupabaseCopilot instructionssupabase/supabase/.github/copilot-instructions.md
Copilot Code Review Instructions ## Review Policy — Read This First You are a code reviewer for a large TypeScript/Next.js/React monorepo. Your reviews must be **low-noise and high-signal**. The team
MicrosoftCopilot instructionsmicrosoft/playwright/.github/copilot-instructions.md
summaries of what the code does. - Do not suggest refactors or improvements unrelated to the PR's stated goal. - NEVER produce a review body or top-level PR overview comment
career-ops-hqCopilot instructionscareer-ops-hq/career-ops/.github/copilot-instructions.md
review` (an empty checklist a maintainer fills in: diff read, behavior validated, tests reviewed, public-code matches checked). Keep the description factual: what changed and why, from the user
diegosouzapwCopilot instructionsdiegosouzapw/OmniRoute/.github/copilot-instructions.md
changes production code in `src/`, `open-sse/`, `electron/`, or `bin/`, it must include automated tests in the same PR. - When reviewing or updating a PR, if the report shows missing
aaif-gooseCopilot instructionsaaif-goose/goose/.github/copilot-instructions.md
GitHub Copilot Code Review Instructions ## Review Philosophy - Only comment when you have HIGH CONFIDENCE (>80%) that an issue exists - Be concise: one sentence per comment when possible - Focus on actionable
Imbad0202Copilot instructionsImbad0202/academic-research-skills/.github/copilot-instructions.md
AI-augmented academic research pipeline with integrity verification
ToolJetCopilot instructionsToolJet/ToolJet/.github/copilot-instructions.md
frontend/assets/images/`. ## Security - No API keys/secrets in client-side code. - Backend: parameterized queries only, never concatenate user input into SQL. ## Common Review Flags - Hardcoded colors (hex/rgb/hsl in JSX or SCSS) - Missing
GitHubCopilot instructionsgithub/awesome-copilot/.github/copilot-instructions.md
following instructions are only to be applied when performing a code review. Use `.github/skills/code-review/SKILL.md` for repository-fit, differentiation, provenance, validation, and editorial-quality review criteria. Apply the deterministic file-format
tirth8205Copilot instructionstirth8205/code-review-graph/.github/copilot-instructions.md
Tools: code-review-graph **This project has a knowledge graph. Start with the code-review-graph MCP tools to narrow scope, then read the source.** The graph is cheaper than
MicrosoftCopilot instructionsmicrosoft/winget-cli/.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
AppleCopilot instructionsapple/foundationdb/.github/copilot-instructions.md
When reviewing PRs, address general code review criteria, but also specifically the following questions: What is it trying to do? Is it correct? Are there bugs? Are there omissions
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
Quality Assurance ### Self-Monitoring - Review responses for accuracy before sending - Check for completeness and relevance - Ensure consistency with previous statements - Validate technical information and code - Confirm alignment with user requirements
MicrosoftCopilot instructionsmicrosoft/windows-rs/.github/copilot-instructions.md
work on this repository. ## Workflow Do not create git commits automatically. The maintainer reviews all changes first and handles commits manually. Make changes locally, run fmt/clippy/tests to verify, and report
MicrosoftCopilot instructionsmicrosoft/garnet/.github/copilot-instructions.md
# Garnet - Copilot Instructions Garnet is a high-performance remote cache-store from Microsoft Research
MicrosoftCopilot instructionsmicrosoft/winget-pkgs/.github/copilot-instructions.md
files describing how to install Windows applications via `winget`. There is no application source code here. The tooling is PowerShell scripts in `Tools/`. ## ⚠️ Critical Performance Rule **Never recursively scan
HashiCorpCopilot instructionshashicorp/terraform-provider-aws/.github/copilot-instructions.md
only. Detect AWS API exceptions with `errs.IsA[*awstypes. ]`. ## Review tone Be specific and actionable. Cite the rule and propose the corrected code. Focus on substance over style: avoid minor comments
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.
