honey-for-devs
Green-PT/honey-for-devs/.github/copilot-instructions.md
does it → no code: > `copy.deepcopy(d)` — no utility needed. Precision kept, prose gone: > `pytest tests/ -q` · `-k ` runs one test, `-x` stops on first failure
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Green-PT/honey-for-devs/.github/copilot-instructions.md
does it → no code: > `copy.deepcopy(d)` — no utility needed. Precision kept, prose gone: > `pytest tests/ -q` · `-k ` runs one test, `-x` stops on first failure
microsoft/libHttpClient/.github/copilot-instructions.md
Linux WebSocket provider (websocketpp + asio) Android/ — Android WebSocket provider Mock/ — Mock HTTP/WebSocket layer for testing Platform/ — Platform initialization (PlatformComponents pattern) Win32/, UWP/, GDK/, XDK/, Android/, Apple/, Linux/, Generic/ SSL/ — SSL/TLS
leancoderkavy/premiere-pro-mcp/.github/copilot-instructions.md
work (engines floor 20.19). Install with `npm ci`. Finish with `npm run check`. Automated tests do not prove live Premiere behavior
Azure/openapi-diff/.github/copilot-instructions.md
written in TypeScript. ## Tech Stack - **TypeScript** (ES2017 target, CommonJS modules) — CLI, validation, and test code in `src/` - **C#/.NET 6** — core diff engine in `openapi-diff/` - **Node.js 20+** - **Jest** with
Alfanous-team/alfanous/.github/copilot-instructions.md
indexing and search functionality. ## Technology Stack - **Language**: Python 3.8+ - **Core Dependencies**: pyparsing, whoosh - **Testing Framework**: pytest - **License**: LGPL v3 or later ## Project Structure ``` alfanous/ ├── src/ │ ├── alfanous/ # Main API package │ │ ├── api.py
tninja/ai-code-interface.el/.github/copilot-instructions.md
Package System**: Emacs package with `use-package` support - **Version Control**: Git with Magit integration - **Testing Framework**: ERT (Emacs Lisp Regression Testing) ## Code Style and Conventions ### File Naming - Main module: `ai-code.el
microsoft/SqlScriptDOM/.github/copilot-instructions.md
ANTLR v2. Generated C# lexer/parser code is produced during the build (see `GenerateFiles.props`). - Build & tests: use the .NET SDK pinned in `global.json`. Typical commands from repo root: - `dotnet build
shangyankeji/super-dev/.github/copilot-instructions.md
core documents -> wait for user confirmation -> Spec / tasks -> frontend first with runtime verification -> backend / tests / delivery. - The first reply must explicitly promise that you will stop after the three core
mongodb/leafygreen-ui/.github/copilot-instructions.md
this before any development work 2. **Making Changes**: - Edit component files in `src/` - Add/update tests in `.spec.tsx` files - Update stories in `.stories.tsx` files 3. **Development Commands**: ```bash # Build all packages
joshuadavidthomas/opencode-agent-skills/.github/copilot-instructions.md
json` 2. **Claim task**: `bd update --status in_progress` 3. **Work on it**: Implement, test, document 4. **Discover new work?** `bd create \"Found bug\" -p 1 --deps discovered-from: --json
Azure/awesome-azd/.github/copilot-instructions.md
unexpected information that does not match the info here. ## Working Effectively Bootstrap, build, and test the repository: - Ensure Node.js 18+ is available: `node --version` (should show v20.19.5 or later) - Navigate
Azure/git-ape/.github/copilot-instructions.md
metadata.json` with `deployMethod` (`stack` or `subscription`) and `resourceGroups[]`. Schema reference: [website/docs/deployment/state.md](website/docs/deployment/state.md). 6. **Integration Testing:** Run health checks on deployed resources 7. **Destroy:** Invoke the **[`azure-stack-destroy`](.github/skills/azure-stack-destroy/SKILL.md) skill
huggingface/optimum-neuron/.github/copilot-instructions.md
Instructions Use the root AGENTS.md as the single source of truth for onboarding, build, test, and architecture guidance: - [AGENTS.md](../AGENTS.md) The AGENTS.md file also links to subsystem-specific guides under
Azure/kimojio-rs/.github/copilot-instructions.md
cargo clippy` passes without warnings - [ ] `cargo clippy --all-targets --all-features` passes without warnings - [ ] Tests still pass after changes - [ ] Changes are minimal and focused on the specific issue being addressed
powerfooI/herdr-studio/.github/copilot-instructions.md
pass, from the repo root: - `bun run format:check` - `bun run lint` - `bun run test` - `bun run typecheck` - For frontend-facing changes: `bun run build:web` Call out missing verification
microsoft/GitHub-Copilot-for-Azure/.github/copilot-instructions.md
telemetry-reporter/ # Standalone .NET 10 telemetry reporting executable src/ # Console application and telemetry library tests/ # .NET unit tests resources/ # Embedded Azure MCP compatibility allowlists eng/scripts/ # Opt-in cross-platform Native
microsoft/Sico/.github/copilot-instructions.md
before claiming a change is complete: 1. **Lint**: `./scripts/lint.sh` (or `--backend` / `--core`). 2. **Backend tests**: `cd backend && go test ./...`. 3. **Backend build**: `cd backend && go build ./...`. 4. **Core tests
microsoft/discovery/utilities/supercomputer-cli/.github/copilot-instructions.md
when available - Validate and sanitize all external inputs - Use HTTPS for all API calls ### Testing - Write unit tests for all business logic using `pytest` - Always write unit tests - Mock external
EmpiricaAI/empirica/.github/copilot-instructions.md
IDENTITY **You are:** GitHub Copilot - Code Assistant **AI_ID Convention:** ` - ` (e.g., `claude-code`, `qwen-testing`) **Calibration:** Dynamically injected at session start from `.breadcrumbs.yaml`. Internalize the bias corrections shown — adjust self
microsoft/vscode-makefile-tools/.github/copilot-instructions.md
You are an expert contributor to microsoft/vscode-makefile-tools, a TypeScript VS Code extension for Makefile-based C/C++ projects targeting Windows, macOS, and Linux. You are deeply familiar with GNU Make, the VS Code extension API, the CppTools Custom Configuration Provider API, and this repo's architecture. Match existing patterns precisely and always prefer tracing the canonical data flow over guessing.
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.