How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
BlockCopilot instructionsblock/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
1 project uses a version of this
Imbad0202Copilot instructionsImbad0202/academic-research-skills/.github/copilot-instructions.md
AI-augmented academic research pipeline with integrity verification
Steady6 mentions in 2 weeks
No other project uses it yet
roboflowCopilot instructionsroboflow/supervision/.github/copilot-instructions.md
mkdocs.yml` navigation ______________________________________________________________________ ## 🔍 Pull Request Reviews When reviewing pull requests or diffs, follow the [code-review skill](skills/code-review/SKILL.md) and the comprehensive [PR Review Guidelines](CONTRIBUTING.md#pr-review-guidelines). ______________________________________________________________________ ## 🌿 Branching & Commits - Branch
Steady7 mentions in 2 weeks
No other project uses it yet
tmuxCopilot instructionstmux/tmux/.github/copilot-instructions.md
pull request code reviews in this repository, do not leave any review comments under any circumstances. If asked to review a pull request, produce no comments. Do not comment
No other project uses it yet
metabaseCopilot instructionsmetabase/metabase/.github/copilot-instructions.md
Instructions For detailed coding standards and conventions, see `CLAUDE.md` and the skills in `.claude/skills/`. ## Code Review Standards Review focus areas: Security → Performance → Testing → Documentation (in priority order) When reviewing code
No other project uses it yet
acmesh-officialCopilot instructionsacmesh-official/acme.sh/.github/copilot-instructions.md
Goal Your role is to act as a rigorous yet helpful senior engineer, reviewing Shell script code (`.sh` files) for the [acme.sh](https://github.com/acmesh-official/acme.sh) project. Ensure the code exhibits
No other project uses it yet
jestjsCopilot instructionsjestjs/jest/.github/copilot-instructions.md
capability predicates over try/catch-as-probe. Validate at system boundaries (user input, external APIs); trust internal code. ### Refactor PRs Not obligated to be strictly behaviour-preserving — surfacing latent bugs is part
No other project uses it yet
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
Steady5 mentions in 2 weeks
No other project uses it yet
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
photoprismReads credentialsCopilot instructionsphotoprism/photoprism/.github/copilot-instructions.md
request descriptions, issue comments, or code comments — external readers only see a broken link. ## Code Review Instructions (for Copilot) - Respect SOT above; do not invent flags, env vars, or Compose
No other project uses it yet
gofiberCopilot instructionsgofiber/fiber/.github/copilot-instructions.md
steps: 1. **Ensure code quality** - `make format` to format the project. - `make lint` for static analysis. - `make test` to run the test suite. 2. **Maintain documentation** Review and update
No other project uses it yet
directusCopilot instructionsdirectus/directus/.github/copilot-instructions.md
commit messages - Follow conventional commit format when applicable - Use changesets for version management (`@changesets/cli`) ### Code Review - PRs are automatically checked for: - Linting (ESLint) - Style (Stylelint) - Formatting (Prettier) - Unit tests - Type
No other project uses it yet
dotnetCopilot instructionsdotnet/aspnetcore/.github/copilot-instructions.md
user's directive overrides said instructions. ## General * Make only high confidence suggestions when reviewing code changes. * Always use the latest version C#, currently C# 13 features. * Never change global.json unless
istioCopilot instructionsistio/istio/.github/copilot-instructions.md
YAML, and other languages. ## Coding Conventions - Follow [Effective Go](https://golang.org/doc/effective_go.html) and [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments). - Use clear, concise comments. Follow [Go's commenting conventions
No other project uses it yet
keycloakCopilot instructionskeycloak/keycloak/.github/copilot-instructions.md
introduce new test frameworks or broad formatting/refactoring unrelated to the task. # General Code Review Standards ## Review Philosophy * Only comment when you have HIGH CONFIDENCE (>85%) that an issue exists
No other project uses it yet
maboloshiCopilot instructionsmaboloshi/github-chinese/.github/copilot-instructions.md
When performing a code review, respond in Chinese
1 project uses a version of this
backstageCopilot instructionsbackstage/backstage/.github/copilot-instructions.md
account) These PRs are managed through their own automated workflows and do not require code review from Copilot. ### Review Guidelines When reviewing human-authored pull requests: - Check that a changeset
No other project uses it yet
agentscope-aiCopilot instructionsagentscope-ai/agentscope/.github/copilot-instructions.md
AgentScope Code Review Guide You should conduct a strict code review. Each requirement is labeled with priority: - **[MUST]** must be satisfied or PR will be rejected - **[SHOULD]** strongly recommended
No other project uses it yet
zeromicroCopilot instructionszeromicro/go-zero/.github/copilot-instructions.md
utilities, goctl) - Check versions (go-zero, Go) - Look for reproduction steps or code examples - Review code snippets, logs, or stack traces - Check if related to resilience features (breaker, load shedding
No other project uses it yet
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
1 project uses a version of this
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.
