How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
DyanGalihCopilot instructionsDyanGalih/spec-kit-memory-hub/.github/copilot-instructions.md
Copilot Instructions This repository is built to work with VS Code Copilot agents memory. For any non-trivial task, memory is part of the workflow, not optional documentation. ## Memory Layers
ElasticCopilot instructionselastic/security-documents-generator/.github/copilot-instructions.md
extended. ## 2) Reuse Elasticsearch helpers (no ad-hoc bulk logic) When reviewing or suggesting Elasticsearch ingest/upload code, map use cases to existing helpers: - In-memory document arrays: - Prefer `ingest(...)` from
gamedevplCopilot instructionsgamedevpl/www.gamedev.pl/.github/copilot-instructions.md
authoritative. ## Current architecture Production games will live in a **dedicated games repo maintained by coding agents**; this app is becoming a catalog, player, and spec-submission surface. Self-hosted agent
Hack23Copilot instructionsHack23/euparliamentmonitor/.github/copilot-instructions.md
each news type / canonical `ARTICLE_TYPE_SLUG` (`breaking`, `week-in-review`, `month-in-review`, `week-ahead`, `month-ahead`, `committee-reports`, `motions`, `propositions`) there is a single unified `news- .md` (`timeout
HMAKT99Copilot instructionsHMAKT99/AKF/.github/copilot-instructions.md
files ```bash akf stamp --agent copilot --evidence " " ``` Evidence examples: "tests pass", "docs reviewed", "refactored from existing code", "generated from spec" ### After completing a task with commits ```bash akf stamp --agent
HolobiomicsLabCopilot instructionsHolobiomicsLab/asb-skill-collections/.github/copilot-instructions.md
software tools for computational LC-MS/MS metabolomics, each derived from a peer-reviewed method paper. **Read [`AGENTS.md`](../AGENTS.md) for the full install + use protocol.** In short: - **Skills** are plain
MicrosoftCopilot instructionsmicrosoft/HOBL/.github/copilot-instructions.md
GitHub Copilot Instructions for HOBL ## PowerShell Coding Standards ### Error Message Formatting When logging or displaying error messages in PowerShell scripts: - Always use the format: `" ERROR - "` (note the spacing) - Leading space
mrlarson2007Copilot instructionsmrlarson2007/aiswarm/.github/copilot-instructions.md
line formatting for constructors, methods, and complex return statements to improve readability and maintainability. ## Code Review Focus Areas - **Design Patterns**: Look for SOLID principles, appropriate abstraction levels - **Test Coverage**: Ensure
mick-gskCopilot instructionsmick-gsk/drift/.github/copilot-instructions.md
github/copilot-instructions.md` After completing a non-trivial coding task (≥10 changed lines in executable source, or high-impact logic), run the **Simplify & Harden** review: - Skill: `.github/skills/simplify-and-harden/SKILL.md` - Three passes: Simplify → Harden → Document
alexey-pelykhCopilot instructionsalexey-pelykh/lhremote/.github/copilot-instructions.md
Copilot Review Instructions — lhremote > Automation toolkit for LinkedHelper.com built on Chrome DevTools Protocol (CDP). ## Project Structure pnpm monorepo with 5 packages: | Package | Purpose | |---------|---------| | `packages/core` | CDP client, account/campaign services, feed parsing
Microsoft AzureCopilot instructionsAzure/agentops/.github/copilot-instructions.md
readiness projection over existing signals; do not create a second exit-code contract. - Trace promotion is review-first. `self-similarity` labels support drift detection, not human-verified correctness. - Doctor
MicrosoftCopilot instructionsmicrosoft/cat/.github/copilot-instructions.md
validated visually and via PR review. To preview locally, serve the root directory with any static file server (e.g., `python -m http.server` or VS Code Live Server extension
Smithbox-aiCopilot instructionsSmithbox-ai/ControlFlow/.github/copilot-instructions.md
agent's tool profile. ## Code Documentation and Language - Before completing an implementation phase, review the changed code for documentation that preserves non-obvious business rules, invariants, exceptions, constraints, and decision
Space-DinosaursCopilot instructionsSpace-Dinosaurs/DinoStack/.github/copilot-instructions.md
loaded: | Signal | Skill | |---|---| | Code edits, debugging, testing, deployment, architecture decisions, git operations, agent orchestration, code review, refactoring, dependency management, project setup | `dinostack` | Copilot description-matches on these signals and injects
zprattCopilot instructionszpratt/lousy-agents/.github/copilot-instructions.md
commands, TDD workflow, tech stack, project structure, code style, dependencies, boundaries, task tracking). Copilot code review always loads it; Claude Code imports it from the root `CLAUDE.md`. - **`.github/instructions/*.instructions.md
Microsoft AzureCopilot instructionsAzure/multi-agent-doc-research/.github/copilot-instructions.md
after the `def` or `class` keyword. - Use blank lines to separate functions, classes, and code blocks where appropriate. ## Edge Cases and Testing - Always include test cases for critical paths
btseeeCopilot instructionsbtseee/clean-code-skills/.github/copilot-instructions.md
Repository-Wide Clean-Code Instructions These instructions guide GitHub Copilot Chat, Copilot code review, and the Copilot coding agent across this repository. In a project that installs this package
kagura-aiCopilot instructionskagura-ai/memory-cloud/.github/copilot-instructions.md
checked in code — these are kept for future re-gating. - PR description accuracy for dependency lists — we update these manually and accept minor drift during iterative review cycles
MicrosoftCopilot instructionsmicrosoft/github-constellation-software/.github/copilot-instructions.md
Markdown and content conventions - Prefer content-only changes in the relevant README over hard-coding page copy in React. - Format resource entries as: `**Resource name** — one-line description. [Link
tygrysoCopilot instructionstygryso/hypotree/.github/copilot-instructions.md
work, perform a second review pass: 1. **Summarize** all assumptions and decisions made during implementation. 2. **Re-examine** the full flow: - If the task involved **code** (create/modify/remove): re-read
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.
