EleSync
darknodebros/EleSync/.github/copilot-instructions.md
When working on the EleSync repository, prefer the EleSync Maintainer custom agent for Python code, docs, tests, packaging, and release workflow changes.
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
darknodebros/EleSync/.github/copilot-instructions.md
When working on the EleSync repository, prefer the EleSync Maintainer custom agent for Python code, docs, tests, packaging, and release workflow changes.
kasuken/vscode-copilot-insights/.github/copilot-instructions.md
VS Code extension project guidelines for GitHub Copilot Insights. Covers project shape, code style, VS Code extension rules, build and test, and repository discipline.
affaan-m/ECC/.github/copilot-instructions.md
coding** — for features larger than a single function, outline phases and dependencies first. 3. **Test-driven** — write the test before the implementation; target 80%+ coverage. 4. **Review before committing** — check
microsoft/vscode/extensions/copilot/.github/copilot-instructions.md
proposed APIs for chat, language models, and editing - **ESBuild**: Bundling and compilation - **Vitest**: Unit testing framework - **Python**: For notebooks integration and ML evaluation scripts ## Validating changes Choose validation based
microsoft/vscode/.github/copilot-instructions.md
organized into key architectural layers: ### Root Folders - `src/`: Main TypeScript source code with unit tests in `src/vs/*/test/` folders - `build/`: Build scripts and CI/CD tools - `extensions/`: Built-in extensions that
huggingface/transformers/.github/copilot-instructions.md
inherit from base classes in the root `/src/transformers` directory. - `/tests`: This contains the core test classes for the library. These are usually inherited rather than directly run. - `/models`: Tests
DietrichGebert/ponytail/.github/copilot-instructions.md
thing that fails if the logic breaks (an assert-based demo/self-check or one small test file; no frameworks, no fixtures). Trivial one-liners need no test
microsoft/PowerToys/.github/copilot-instructions.md
PowerToys AI contributor guidance
microsoft/TypeScript/.github/copilot-instructions.md
pipelines. Most compiler development takes place in `tsc/internal`, and most behaviors can be tested via compiler tests. Most development on the codebase is in Go. Standard Go commands and practices
supabase/supabase/.github/copilot-instructions.md
every PR - **Typos or spelling** — Automated typo detection runs on every PR - **Missing tests for trivial changes** — Handled by topic-specific test instructions - **Import ordering or grouping** — Handled by linter
bytedance/deer-flow/.github/copilot-instructions.md
make install ``` ### B. Backend CI-equivalent validation Run from `backend/`: ```bash make lint make test ``` Validated results: - `make lint`: pass (`ruff check .`) - `make test`: pass (`277 passed, 15 warnings
rtk-ai/rtk/.github/copilot-instructions.md
status rtk git status git log -10 rtk git log -10 cargo test rtk cargo test cargo clippy --all-targets rtk cargo clippy --all-targets grep -r "pattern
headroomlabs-ai/headroom/.github/copilot-instructions.md
Behavior Proof" with environment, exact commands or steps, observed result, and what was not tested. 3. Be strict about contributor verification: missing tests, missing runtime evidence, or placeholder PR text
career-ops-hq/career-ops/.github/copilot-instructions.md
were asked to reproduce a bug, brief a pull request, write or fix a test, re-sync a translation, find stale documentation, or make any change to the code (this
diegosouzapw/OmniRoute/.github/copilot-instructions.md
OmniRoute PR and Coverage Instructions - Treat `npm run test:coverage` as a required gate for PR work. - The repository minimum is `60%` for statements, lines, functions, and branches
cline/cline/.github/copilot-instructions.md
gRPC-like protocol over VS Code message passing. Schemas in `proto/`. - **MCP**: `src/services/mcp/McpHub.ts`. ## Build & Test (Critical — non-obvious commands) - **Build**: `bun run compile` — NOT `bun run build`. - **Watch
mvanhorn/last30days-skill/.github/copilot-instructions.md
specific additions. See AGENTS.md for the shared cross-tool governance layer. # Copilot-specific guidance ## Test generation - Prefer unittest.TestCase for generated tests to match the existing test suite. - Mock external calls
microsoft/autogen/.github/copilot-instructions.md
seconds. poe pyright # Takes 41 seconds. Set timeout to 120+ seconds. # Individual package testing (core package example) poe --directory ./packages/autogen-core test # Takes 10 seconds. Set timeout to 60+ seconds. # Documentation
aaif-goose/goose/.github/copilot-instructions.md
What Our CI Checks (`.github/workflows/ci.yml`) **Rust checks:** - `cargo fmt --check` - Code formatting (rustfmt) - `cargo test --jobs 2` - All tests - `cargo clippy --all-targets -- -D warnings` - Linting (clippy) **Desktop app checks
ToolJet/ToolJet/.github/copilot-instructions.md
only. No Redux/MobX/Recoil. - Use `shallow` comparison in `useStore` when selecting objects/arrays. Flag missing `shallow`. ## Tests Rules: `.github/instructions/frontend-tests.instructions.md`. How to write one: `frontend/src/test/README.md`. Reject any spec that would still pass against
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.