How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Microsoft AzureCopilot instructionsAzure/iotedge/.github/copilot-instructions.md
utilities live in `edge-util/` (Option type, Preconditions, storage abstractions, RocksDB bindings). ## Build and Test ### C# (.NET 8.0) Solution: `Microsoft.Azure.Devices.Edge.sln` ```bash # Build everything (Linux) scripts/linux/buildBranch.sh -c Release --no-rocksdb
GitHubCopilot instructionsgithub/gh-stack/.github/copilot-instructions.md
branches and pull requests. Uses Cobra for commands, bubbletea/lipgloss for TUI, and `stretchr/testify` for tests. ## Build and validate ```sh go mod download # install deps go build -o gh-stack . # build
MicrosoftCopilot instructionsmicrosoft/ai-dev-gallery/.github/copilot-instructions.md
PascalCase` ### XAML Conventions - Use WinUI 3 controls - Follow accessibility guidelines (narrator support, keyboard navigation) ## Testing Requirements ### Unit Tests - Location: `AIDevGallery.Tests/UnitTests/` - Framework: MSTest - Run with filter: `--filter "FullyQualifiedName~UnitTests"` ### When
MicrosoftCopilot instructionsmicrosoft/win32metadata/.github/copilot-instructions.md
Commands ```powershell # Full build (25-30 min): build tools, scrape headers, emit winmd, package, test ./DoAll.ps1 -Clean # Incremental build (faster, skips packages/samples) ./DoAll.ps1 -ExcludePackages -ExcludeSamples # Build just the build tools
MicrosoftCopilot instructionsmicrosoft/hve-core/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for hve-core
yigitkonurCopilot instructionsyigitkonur/cli-continues/.github/copilot-instructions.md
always a bug; changes to `SessionSource` require coordinated updates in the registry, fixtures, and tests ## Code Quality - Biome handles all formatting and style — do not introduce ESLint, Prettier, or TSLint
HexmosTechCopilot instructionsHexmosTech/git-lrc/.github/copilot-instructions.md
Having fallbacks creates very confusing program behavior. When you want to run a test - always run the most specific test you want to run. Don't run all or other
MicrosoftCopilot instructionsmicrosoft/pict/.github/copilot-instructions.md
PICT Repository Development Guidelines Comprehensive instructions for developing in the PICT (Pairwise Independent Combinatorial Testing) repository ## Project Overview PICT (Pairwise Independent Combinatorial Testing) is a Microsoft open-source command-line
yohey-wCopilot instructionsyohey-w/multi-agent-shogun/.github/copilot-instructions.md
GitHub Copilot CLI + tmux multi-agent parallel dev platform with sengoku military hierarchy
MicrosoftCopilot instructionsmicrosoft/mxc/.github/copilot-instructions.md
from names. - Follow any matching file-scoped instructions under `.github/instructions/`. - Inspect nearby code and tests before editing. Reuse existing abstractions and error types. - Do not hand-edit generated files
specstoryaiCopilot instructionsspecstoryai/getspecstory/.github/copilot-instructions.md
code is DRY, and doesn't replicate the same or similar code - for test cases, ensure a data-driven approach is being used rather than lots of repetitive test code
GitHubCopilot instructionsgithub/gh-skyline/.github/copilot-instructions.md
Packages - Functions and methods - Types and interfaces - Exported variables and constants - Write unit tests for core functionality - Keep functions focused and manageable (generally under 50 lines) - Use error handling patterns
MicrosoftCopilot instructionsmicrosoft/waza/.github/copilot-instructions.md
this **once** at the start of any session before `go build`, `go test`, or `golangci-lint run`. ### 2. Never restage a regenerated `web/dist/index.html` `web/dist/assets/*` is gitignored but `web/dist/index.html` **is tracked
MicrosoftCopilot instructionsmicrosoft/gctoolkit/.github/copilot-instructions.md
Vert.x-based messaging and event handling infrastructure - `sample/` - Example usage and sample applications - `IT/` - Integration tests - `gclogs/` - Test data and sample GC logs ## Key Technologies - **Java 21+** with module system (module-info.java
sipyourdrink-ltdCopilot instructionssipyourdrink-ltd/bernstein/.github/copilot-instructions.md
scheduling agents/ # Lifecycle, spawning, identity, signals tasks/ # Lifecycle, store, claim, retry, models quality/ # Gates, testing, review, architecture security/ # Auth, RBAC, permissions, compliance observability/ # Metrics, tracing, logging, alerting protocols
SupabaseCopilot instructionssupabase/supabase-swift/.github/copilot-instructions.md
documentation is up to date - Check if examples are up to date - Check if tests are comprehensive and cover all critical paths ## Repository Overview @../AGENTS.md
datalayerCopilot instructionsdatalayer/jupyter-mcp-server/.github/copilot-instructions.md
Notebooks. The project uses a modern Python build system with hatch, and includes comprehensive testing, linting, and documentation. ## Working Effectively ### Environment Setup - **Python Requirements**: Python 3.10 or higher (tested with
MicrosoftCopilot instructionsmicrosoft/CSS-Exchange/.github/copilot-instructions.md
SpellCheck.ps1`. Use: `"Use the code-creator agent to create a new function"` - **pester-test** — Creates Pester tests following repo patterns and performance rules. Use: `"Use the pester-test agent
MicrosoftCopilot instructionsmicrosoft/griffel/.github/copilot-instructions.md
yarn --version` should show 4.3.1) - Uses Nx monorepo for task orchestration ### Bootstrap, Build, and Test **CRITICAL: NEVER CANCEL long-running commands. Set timeouts appropriately.** ```bash # Install dependencies - takes ~2 minutes
MicrosoftCopilot instructionsmicrosoft/prompty/.github/copilot-instructions.md
import VERSION from ...core.types import Message from ..openai.executor import _build_options, _message_to_wire ``` - **Tests use absolute imports** from the package: ```python from prompty.core.types import Message, TextPart from prompty.providers.openai.executor import
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.
