How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
ruilisiCopilot instructionsruilisi/lsbot/.github/copilot-instructions.md
refs to click/type/drag/select 3. Re-snapshot if the page changed ## Skills ### /review-code - Code Review After Changes Review code changes in the current branch compared to main. Provide structured feedback
jamditisCopilot instructionsjamditis/claude-skills-journalism/.github/copilot-instructions.md
conventions live in [CLAUDE.md](../CLAUDE.md). Both this file and CLAUDE.md are read by Copilot code review (cap ~4,000 chars each). This file lists the rules worth named attention
MicrosoftCopilot instructionsmicrosoft/mssql-django/.github/copilot-instructions.md
wide technical reference: SQL Server limitations, coding patterns, common errors, and testing commands. - **`AGENTS.md`** holds project facts, contribution conventions, and cross-cutting review judgment. - **`.github/instructions/*.instructions.md`** hold path-specific review
Tiberriver256Copilot instructionsTiberriver256/mcp-server-azure-devops/.github/copilot-instructions.md
configs for unit/int/e2e tests) - `ts-node-dev` - Development server with auto-restart - `oxlint` + `oxfmt` - Code quality and formatting - `husky` - Git hooks for commit validation **CI/CD:** - GitHub Actions workflow: `.github/workflows/main.yml` - Runs
MicrosoftCopilot instructionsmicrosoft/MHA/.github/copilot-instructions.md
verify no ESLint errors ### TDD Approach for Bug Fixes When fixing bugs identified in code reviews or reported issues: 1. **Write failing test first**: Create a test that demonstrates
mrwoguCopilot instructionsmrwogu/promptscript/.github/copilot-instructions.md
Commander.js - Testing: Vitest - Linting: ESLint + Prettier - Project: PromptScript ## Engineering Standards ### graph-first - Use code-review-graph MCP tools BEFORE Grep/Glob/Read when exploring the codebase - Exploring code: use semantic_search_nodes
MicrosoftCopilot instructionsmicrosoft/slow-cheetah/.github/copilot-instructions.md
Copilot instructions for this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Run the `.github/Prime-ForCopilot.ps1` script (once) before running any `dotnet
MicrosoftCopilot instructionsmicrosoft/lisa/.github/copilot-instructions.md
affected LISA features 3. **Image Selection** - Choose appropriate Azure marketplace images ## Copilot Instructions for Code Reviews **MANDATORY REQUIREMENT:** Every code review must include a test suggestion using the Quick Reference
MicrosoftCopilot instructionsmicrosoft/ApplicationInsights-node.js/.github/workflows/copilot-instructions.md
loops and inefficient patterns - Prefer optimized patterns and consider memoization for expensive operations --- ## 📋 Code Review Checklist Before suggesting code, ensure: - [ ] Only official APIs and standard library features are used
MicrosoftCopilot instructionsmicrosoft/fabric-cicd/.github/copilot-instructions.md
enum in `src/fabric_cicd/constants.py`. Always reference that file for the current list — do not hard-code item type strings without verifying them against the enum. The publish/unpublish dependency order is defined
AvdLeeCopilot instructionsAvdLee/Core-Data-Agent-Skill/.github/copilot-instructions.md
GitHub Copilot Instructions: Agent Skills Expert Review code changes as an **Agent Skills expert**, focusing on the [Agent Skills open format](https://agentskills.io/home) specification and best practices. ## Core Agent
DitriXNewCopilot instructionsDitriXNew/EDT-MCP/.github/copilot-instructions.md
stuck after 2 attempts, architectural decisions 🎯 Select Options - Present 2-5 choices for decisions 📝 Review Code - Security-sensitive or complex implementations ⚠️ Confirm Action - Before deletions, schema changes, breaking changes 🖼️ Read
tninjaCopilot instructionstninja/ai-code-interface.el/.github/copilot-instructions.md
Code Manipulation**: Change code, implement TODOs, explain code, fix errors 4. **Agile Development**: TDD cycle support, refactoring assistance 5. **Git Integration**: Diff review, git blame/log analysis, Magit transient menus
MicrosoftCopilot instructionsmicrosoft/SqlScriptDOM/.github/copilot-instructions.md
Type vResult = this.FragmentFactory.CreateFragment ()] { ... } : ( alternatives ) ;` — this pattern initializes an AST fragment via FragmentFactory. - Parser-generated code frequently uses `Match( , CodeGenerationSupporter. )` and `ThrowParseErrorException("SQLxxxx", ...)` for diagnostics. - The codebase prefers using the factory
shangyankejiCopilot instructionsshangyankeji/super-dev/.github/copilot-instructions.md
code before confirmation. - If the user requests a UI redesign or says the UI is unsatisfactory, first update `output/*-uiux.md`, then redo the frontend, and rerun frontend runtime + UI review
Microsoft AzureCopilot instructionsAzure/awesome-azd/.github/copilot-instructions.md
version (e.g., `app-name@1.0.0`) - List all Azure services and dependencies - Include infrastructure as code (Bicep or Terraform) configuration Example azure.yaml structure: ```yaml name: my-ai-app metadata: template
Microsoft AzureCopilot instructionsAzure/git-ape/.github/copilot-instructions.md
never reference parent variables directly from inner-scope templates ## Deployment Workflow ### Interactive Mode (VS Code / local CLI) 1. **Requirements Gathering:** Collect all necessary parameters before generating templates 2. **Template Validation
powerfooICopilot instructionspowerfooI/herdr-studio/.github/copilot-instructions.md
These are build artifacts; they must not be edited or committed. ## Review priorities When reviewing pull requests, focus on: - Correctness of the Bun bridge: HTTP/WebSocket message handling, socket lifecycle, reconnection
MicrosoftCopilot instructionsmicrosoft/GitHub-Copilot-for-Azure/.github/copilot-instructions.md
account show --query name -o tsv`) and key decisions off the command's exit code. - **Keep CLI install hints in the repo's standard call form**, e.g. `mcp_azure
EmpiricaAICopilot instructionsEmpiricaAI/empirica/.github/copilot-instructions.md
Create checkpoint at release points empirica checkpoint-create --session-id --message "Feature complete" ``` **Code Review Patterns:** 1. PREFLIGHT before review - assess familiarity with codebase area 2. Log unknowns for areas
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.
