How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/vscode-powerquery-sdk/.github/copilot-instructions.md
This repository contains the VS Code extension for the "Power Query Connector SDK". This document provides context to help GitHub Copilot assist with development tasks, particularly converting test frameworks
marckrennCopilot instructionsmarckrenn/rtfmbro-mcp/.github/copilot-instructions.md
Copilot Instructions for Package Documentation ## Package Documentation Policy * Before using any package, module, or library, ALWAYS consult its documentation — your internal knowledge may be outdated and could cause errors
Microsoft AzureCopilot instructionsAzure/api-management-self-hosted-gateway/.github/copilot-instructions.md
gateway source code—only the Helm chart, packaged chart archives, CI workflows, and documentation. The single Helm chart lives in `helm-charts/azure-api-management-gateway/`. Packaged `.tgz` releases and `index.yaml` sit alongside
selfagencyCopilot instructionsselfagency/opilot/.github/copilot-instructions.md
Agent: Visual Studio Code Extension Integrating Ollama into GitHub Copilot Chat Welcome! This document guides you through the recommended workflows, conventions, and tooling when working on the **Opilot** VS Code
MicrosoftCopilot instructionsmicrosoft/Agents-for-js/.github/copilot-instructions.md
import tsx 'packages/agents-hosting/test/**/*.test.ts' # one package ``` Run `npm run repo:doctor` after structural, package, documentation, build-reference, dependency, API-baseline, test-agent, Docker, or runtime-configuration changes. Its ESLint-style
HashiCorpCopilot instructionshashicorp/web-unified-docs/.github/copilot-instructions.md
Next.js application, build and content-tooling scripts, API routes, tests, and the Markdown/MDX documentation under `content/`. These repository-wide instructions are intentionally small and apply to every pull request. They
MicrosoftCopilot instructionsmicrosoft/kiota-dotnet/.github/copilot-instructions.md
body] [optional footer(s)] ``` ### Types - **feat**: A new feature - **fix**: A bug fix - **docs**: Documentation only changes - **style**: Changes that do not affect the meaning of the code (white-space
Microsoft AzureCopilot instructionsAzure/cyclecloud-slurm/.github/copilot-instructions.md
unnecessarily complex logic: -10 - Otherwise: 0 Regression Risk (10) - Introduces regression risk not documented in PR description or README: -10 - Otherwise: 0 Exception Handling (10) - Exceptions not handled or errors
MicrosoftCopilot instructionsmicrosoft/chartifact/.github/copilot-instructions.md
Copilot Instructions for Chartifact Welcome to the Chartifact codebase! This document provides essential guidance for AI coding agents to be productive in this repository. Chartifact is a low-code framework
MRCalderon3DCopilot instructionsMRCalderon3D/everything-game-dev-code/.github/copilot-instructions.md
loose prompt collection. Prioritize: - engine isolation - reusable workflow patterns - explicit ownership - source-of-truth documentation - structured deliverables over ad hoc output ## How To Navigate The Repository - Start with `README.md
PeargentCopilot instructionsPeargent/peargent/.github/copilot-instructions.md
explain test failures unless subtle --- ## Import Rule (CRITICAL) ### For User-Facing Code (Examples, Documentation, etc) ✅ **MUST** use public APIs: ```python from peargent import create_agent, create_tool, create_pool from
putervisionCopilot instructionsputervision/vision-memory-mcp/.github/copilot-instructions.md
create", type: "task", title: "...", session_id: session_id)`. - **Making a design or implementation decision**: Document it with `manage_nodes(action: "create", type: "decision", title: "...", metadata: { "rationale": "..." }, session_id: session
Microsoft AzureCopilot instructionsAzure/AzureLocal-Supportability/.github/copilot-instructions.md
guidelines) ## PR Review Guidelines and Checklists ### Review Process Guidance - Focus on consistency with existing documentation and templates - Limit comments to substantive issues (3-5 max per PR) - Use concise, actionable
simonkurtz-MSFTCopilot instructionssimonkurtz-MSFT/drawio-mcp-server/.github/copilot-instructions.md
update a `.drawio` file in the repository with that content. - Store generated Markdown documents in `docs/` and update any links accordingly. - Prioritize speed, memory footprint, and maintainability in all implementations
swt-labsCopilot instructionsswt-labs/vibe-better-with-claude-code-vbw/.github/copilot-instructions.md
hook behavior, search `testing/` for the corresponding contract before editing. The test usually documents the intended invariant better than a quick skim of the implementation. - Keep the repo zero-dependency
MicrosoftCopilot instructionsmicrosoft/cat-agent-skills/.github/copilot-instructions.md
running agent ever need this sentence to do the task?* If no — it's documentation, and belongs in the `README.md`. Apply the test to the sentence's **reader**: an instruction
Fighter90Copilot instructionsFighter90/career-ops-ui/.github/copilot-instructions.md
When in doubt 1. Read [`../docs/architecture/OVERVIEW.md`](../docs/architecture/OVERVIEW.md). 2. Run `npm test` — the suite documents existing invariants. 3. Check the latest release REVIEW in `docs/reviews/`. 4. Ask the user
vanillagreencomCopilot instructionsvanillagreencom/kendex/.github/copilot-instructions.md
finding. Do not repeat a finding class that a stated decline or a documented accepted trade-off already answers. Reopen it only when the relevant code has changed. Report
AsiaOstrichCopilot instructionsAsiaOstrich/universal-dev-standards/skills/tools/copilot/copilot-instructions.md
Conventional Commits format: ``` ( ): ``` **Types:** - `feat` - New feature - `fix` - Bug fix - `refactor` - Code refactoring - `docs` - Documentation - `test` - Tests - `chore` - Maintenance **Examples:** - `feat(auth): add OAuth2 login` - `fix(api): handle null user
MicrosoftCopilot instructionsmicrosoft/atlas-design/.github/copilot-instructions.md
package npm run build:js # Build JS package npm run build:site # Build documentation site # Lint npm run lint # All packages npm run lint:css # SCSS only npm run lint
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.
