How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/autogen/.github/copilot-instructions.md
seconds. poe pyright # Takes 41 seconds. Set timeout to 120+ seconds. # Individual package testing (core package example) poe --directory ./packages/autogen-core test # Takes 10 seconds. Set timeout to 60+ seconds. # Documentation
aaif-gooseCopilot instructionsaaif-goose/goose/.github/copilot-instructions.md
What Our CI Checks (`.github/workflows/ci.yml`) **Rust checks:** - `cargo fmt --check` - Code formatting (rustfmt) - `cargo test --jobs 2` - All tests - `cargo clippy --all-targets -- -D warnings` - Linting (clippy) **Desktop app checks
ToolJetCopilot instructionsToolJet/ToolJet/.github/copilot-instructions.md
only. No Redux/MobX/Recoil. - Use `shallow` comparison in `useStore` when selecting objects/arrays. Flag missing `shallow`. ## Tests Rules: `.github/instructions/frontend-tests.instructions.md`. How to write one: `frontend/src/test/README.md`. Reject any spec that would still pass against
HashiCorpCopilot instructionshashicorp/vault/.github/copilot-instructions.md
style, package organization, error handling, and idiomatic patterns - **[golang_tests.instructions.md](instructions/generic/golang_tests.instructions.md)**: Best practices for writing tests in Go, including table-driven tests, test structure, and integration testing ### Ember.js UI Development - **[ember_general.instructions.md
MicrosoftCopilot instructionsmicrosoft/WSL/.github/copilot-instructions.md
Linux-side WSL components - `src/shared/` — Shared code between Windows and Linux - `test/windows/` — Windows-based tests (TAEF framework) - `test/linux/unit_tests/` — Linux unit test suite - `doc/` — Documentation source (MkDocs) - `tools/` — Build and deployment
GitHubCopilot instructionsgithub/github-mcp-server/.github/copilot-instructions.md
github-mcp-server (stdio MCP server - **this is the main focus**) - **Secondary Package:** mcpcurl (testing utility - don't break it, but not the priority) - **Framework:** Uses modelcontextprotocol/go-sdk for MCP protocol
mukul975Copilot instructionsmukul975/Anthropic-Cybersecurity-Skills/.github/copilot-instructions.md
Fraud Impact) | ### Subdomains (Choose One) - **web-application-security** — OWASP, API, web app testing - **network-security** — Network tools, protocols, monitoring - **penetration-testing** — General penetration testing methodology - **red-teaming** — Simulating advanced attackers
tirth8205Copilot instructionstirth8205/code-review-graph/.github/copilot-instructions.md
graph is cheaper than scanning files and gives you structural context (callers, dependents, test coverage) that file search cannot. ### When to use graph tools FIRST - **Exploring code**: `semantic_search_nodes
gastownhallCopilot instructionsgastownhall/beads/.github/copilot-instructions.md
Tech Stack - **Language**: Go 1.21+ - **Storage**: Dolt (version-controlled SQL database) - **CLI Framework**: Cobra - **Testing**: Go standard testing + table-driven tests - **CI/CD**: GitHub Actions - **MCP Server**: Python (integrations/beads-mcp/) ## Coding Guidelines
MicrosoftCopilot instructionsmicrosoft/winget-cli/.github/copilot-instructions.md
src/PowerShell`) - Microsoft.WinGet.Client and Microsoft.WinGet.Configuration cmdlets - **Configuration system** - DSC-based system configuration using WinGet ## Building, Testing, and Running ### Initial Setup Use a configuration file in `.config` as in `winget configure .config/configuration.winget
nukeopCopilot instructionsnukeop/nuclear/.github/copilot-instructions.md
linting. - Storybook - used for demoing UI components. - Vite - build tool - Vitest - for all tests - Lucide React - icon library - motion and tw-animate-css - for animations - TanStack Router - chosen solution
MicrosoftCopilot instructionsmicrosoft/react-native-windows/.github/copilot-instructions.md
React Native runtime - **JavaScript/TypeScript tooling** for development experience - **Sample applications** and test suites - **Documentation** and build tools ### Key Architecture Components - **Paper Architecture** (legacy): UWP XAML-based renderer - **Fabric Architecture
triggerdotdevCopilot instructionstriggerdotdev/trigger.dev/.github/copilot-instructions.md
prefer using isomorphic code like fetch, ReadableStream, etc. instead of Node.js specific code. Our tests are all vitest. We use prisma in internal-packages/database for our database interactions using
MicrosoftCopilot instructionsmicrosoft/pyright/.github/copilot-instructions.md
language server (`pyright-langserver`), and a VS Code extension (`vscode-pyright`). ## Build and Test ```bash # Install all packages (from repo root) pnpm install # Build the core library cd packages/pyright-internal && pnpm
open-metadataCopilot instructionsopen-metadata/OpenMetadata/.github/copilot-instructions.md
case considerations - Provide clear documentation and usage examples - Explain technical decisions and trade-offs - Test solutions mentally before presenting them ### Creative and Content Tasks - Generate original, engaging content tailored
AgriciDanielCopilot instructionsAgriciDaniel/claude-obsidian/.github/copilot-instructions.md
lint/query read-only. - Preserve vault path containment and product/vault separation. - Add hermetic regression tests for behavior changes and run `make test`. - Do not add secrets, private paths, unsupported capability claims
NanmiCoderCopilot instructionsNanmiCoder/cc-haha/.github/copilot-instructions.md
edit. Use the root completion and authorization boundaries; consult `docs/internals/contributing.md` for task-specific testing and failure diagnosis. Continue scoped local implementation, deterministic checks, and fixes without asking at each step
InsForgeCopilot instructionsInsForge/InsForge/.github/copilot-instructions.md
TypeScript schemas - `/docker-init`: Docker initialization scripts - `/openapi`: API documentation in OpenAPI format - `/tests`: Comprehensive test suites ## Libraries and Frameworks ### Backend - Express.js for REST API framework - PostgreSQL with pg driver
MicrosoftCopilot instructionsmicrosoft/windows-rs/.github/copilot-instructions.md
crate. - `crates/tools/*` - code generators and CI helpers, run via `cargo run -p tool-*`. - `crates/tests/*/*` - test crates; `crates/tests/libs/ ` mirrors each library crate (e.g. `test_reactor`, `test-webview`). Crate names are `test
MicrosoftCopilot instructionsmicrosoft/garnet/.github/copilot-instructions.md
unified single-store** design — see the Architecture section below for the current model. ## Build, Test, and Lint ```bash # Build the entire solution dotnet build # Run all Garnet tests GARNET_TEST
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.
