How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
raye-dengCopilot instructionsraye-deng/open-code-review/.github/copilot-instructions.md
Open Code Review - AI Code Quality Gate When writing or reviewing code, check for AI-specific defects: ## Key Checks - **Phantom imports**: Verify all package imports reference real, existing packages - **Stale
veritasfuji-japanCopilot instructionsveritasfuji-japan/veritas_os/.github/copilot-instructions.md
Copilot Role GitHub Copilot is primarily used for: - GitHub-native PR review - local coding assistance - focused implementation suggestions - small bug and test-gap detection - concise explanations of changed code Keep
fluttersdkCopilot instructionsfluttersdk/wind/.github/copilot-instructions.md
policy (binding) The 90% line-coverage gate is the floor, not the target. - Adding code drops coverage? Add tests in the SAME change set to land back at ≥ 90%. Never
BinaryMeadowCopilot instructionsBinaryMeadow/gridwatch/.github/copilot-instructions.md
first user.message starts with "Researching: " isReview: boolean // true if events.jsonl contains "agent_type":"code-review" agentTypes: string[] // all agent_type values found in events.jsonl (e.g. ["explore", "security-reviewer"]) researchReports: string
RafaelGorskiCopilot instructionsRafaelGorski/Problem-Based-SRS/.github/copilot-instructions.md
designed for AI agent consumption (AgentSkills standard) - **AI Agent**: Tools like GitHub Copilot, Claude Code, or similar assistants - **Trunk-Based Development**: All changes committed directly to main branch ## Quality Standards
chrisgleissnerCopilot instructionschrisgleissner/c64bridge/.github/copilot-instructions.md
Review Required**: All pull requests require human approval. Treat agent contributions like code from a junior developer—review thoroughly, request changes, and iterate. ## Pull Request Guidelines - Keep PRs focused
dirnbauerCopilot instructionsdirnbauer/webconsulting-skills/.github/copilot-instructions.md
owning skills, for example `php-modernization`, `typo3-content-blocks`, and `typo3-update`. - Always review AI-generated code before committing. - When multiple skills are relevant, combine them, for example `typo3-rector
blundergoatCopilot instructionsblundergoat/goat-flow/.github/copilot-instructions.md
cleanup, revert, or apply approval. - Do not delete docs without replacement or modify .env/secrets. - Coding agents never run `git commit` or `git push`; the user performs both manually. - Forwarded
dynatrace-ossCopilot instructionsdynatrace-oss/dynatrace-managed-mcp/.github/copilot-instructions.md
versioning ## Development Guidelines - **Complete implementations**: No TODOs, placeholders, or missing pieces - **Readability over performance**: Code should be clear and maintainable - **Add tests for bugs**: When fixing bugs, add test cases
MicrosoftCopilot instructionsmicrosoft/powerbi-visuals-mekkochart/.github/copilot-instructions.md
changelog.md` → `info`/`warning`. - For new public APIs — add usage examples → `info`. ### 9) Code quality & architecture (senior review mindset) - Briefly summarize PR purpose and affected areas (render, data, settings, UI). - Highlight
MicrosoftCopilot instructionsmicrosoft/trident/.github/copilot-instructions.md
Architecture & structural soundness" sections apply to **both** writers (follow them when generating new code) and reviewers (see [Reviewer etiquette](#reviewer-etiquette-nits--architecture) for when to surface them). ## PR Review
MicrosoftCopilot instructionsmicrosoft/vscode-documentdb/.github/copilot-instructions.md
Never bulk-load it. Plans and reviews there are evidence of past reasoning, not a description of the product today. - **On conflict, the code wins for behavior; active docs
TechopolisCopilot instructionsTechopolis/swift-agents/.github/copilot-instructions.md
SwiftUI code without mobile-a11y-specialist review 4. Do NOT write concurrent code without concurrency-specialist review 5. Do NOT handle credentials or encryption without swift-security-specialist review
JeremyDev87Copilot instructionsJeremyDev87/codingbuddy/.github/copilot-instructions.md
Copilot Code Review Instructions ## Review Priority Levels - **🔴 CRITICAL (Block merge)**: Security vulnerabilities, logic errors, breaking changes, data loss risks - **🟡 IMPORTANT (Requires discussion)**: Code quality issues, missing tests, performance bottlenecks, architectural
erevusobolusCopilot instructionserevusobolus/THERION-SYSTEM/.github/copilot-instructions.md
error, fix, crash, bug, refactor, docs, readme, testing, vscode, linting, support.md 6 workspace, profiling, code review DEFAULT (unclear context) strategic.md -- ═══════════════════════════════════════════════════════════════════════════════ MEMORY PROTOCOL -- 3-TIER ADAPTIVE MEMORY ═══════════════════════════════════════════════════════════════════════════════ THERION uses
NVIDIACopilot instructionsNVIDIA/holodeck/.github/copilot-instructions.md
fixes - `docs:` - Documentation - `refactor:` - Code refactoring - `test:` - Test additions/changes - `chore:` - Maintenance tasks --- ## Getting Help - Check existing issues and PRs for context - Review `docs/` directory for detailed documentation - Look at `examples
wictorwilenCopilot instructionswictorwilen/MRSF/.github/copilot-instructions.md
Review Sidecar Format), also known as **Sidemark**, is a specification plus tooling for storing review comments in sidecar files alongside Markdown documents. The canonical spec is `MRSF-v1.0.md`. ## Repository Architecture This
Microsoft AzureCopilot instructionsAzure/apiops-cli/.github/copilot-instructions.md
integration of the entire branch into main**, so describe what's being integrated. ## Code Review Requirement **After any changes to files under `src/` or `tests/`**, a code review MUST
Microsoft AzureCopilot instructionsAzure/apiops-cli/.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
Microsoft AzureCopilot instructionsAzure/fleet-networking/.github/copilot-instructions.md
verify the plan with: "Are you happy with this implementation plan?" before proceeding with code changes. 6. Reference related breadcrumbs when a task builds on previous work. 7. Before concluding
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.
