teams-mcp
floriscornel/teams-mcp/.github/copilot-instructions.md
Commands ```bash npm run build # clean + tsc npm run dev # tsx watch src/index.ts npm test # vitest run npm run test:watch # vitest (watch mode) npm run test:coverage # vitest with
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
floriscornel/teams-mcp/.github/copilot-instructions.md
Commands ```bash npm run build # clean + tsc npm run dev # tsx watch src/index.ts npm test # vitest run npm run test:watch # vitest (watch mode) npm run test:coverage # vitest with
dynatrace-oss/dynatrace-mcp/.github/copilot-instructions.md
user asks you to solve a bug in the project, consider adding a test case. ## Repo Structure The repository is structured as follows: - `src/`: Contains the source code
Azure/azure-sdk-tools/.github/copilot-instructions.md
found in the codebase - Each tool should be self-contained with its own README, tests, and CI configuration ## Repository Structure - `/tools/` - Individual tools organized by name, each
Azure/terraform-azurerm-avm-ptn-alz/.github/copilot-instructions.md
Instructions for developing and maintaining Azure Verified Modules for Terraform.
jasonsuhari/gridbash/.github/copilot-instructions.md
user workflows. - Ratatui layout behavior in small terminals and keyboard handling conflicts. - Missing regression tests for behavior that can be exercised deterministically. Use these severities: - `P0`: immediate security compromise, destructive
AndrewAltimit/template-repo/.github/copilot-instructions.md
cache prevention via environment variables - **Multi-stage CI/CD** - format, lint-basic, lint-full, security, test stages ## Review Focus Areas ### PRIORITIZE reviewing 1. **Container configurations** - Dockerfile correctness, security, user permissions
Azure/cosmos-explorer/.github/copilot-instructions.md
Copilot Instructions for Cosmos Explorer ## Build, Test, and Lint **To build the project, use the `/build` skill.** It handles dependency checks (`npm install`) and all build variants. See `.github/skills/build/SKILL.md
microsoft/eval-guide/.github/copilot-instructions.md
Skill Routing | Task | Prompt File | |---|---| | Full eval lifecycle | `eval-guide.prompt.md` | | Create eval plan | `eval-suite-planner.prompt.md` | | Generate test cases | `eval-generator.prompt.md` | | Interpret results | `eval-result-interpreter.prompt.md` | | Triage failures | `eval-triage-and-improvement.prompt.md` | | Methodology Q&A | `eval-faq.prompt.md` | ## Key Conventions
microsoft/terraform-provider-fabric/.github/copilot-instructions.md
github.com/microsoft/fabric-sdk-go) (`github.com/microsoft/fabric-sdk-go`) - **Task Runner:** [Task](https://taskfile.dev/) — all build, test, lint, and doc commands are defined in `Taskfile.yml` - **Linters:** `golangci-lint`, `markdownlint`, `tflint` - **Doc Generator:** `tfplugindocs` ## Environment
microsoft/VirtualClient/.github/copilot-instructions.md
cross-platform benchmarking framework by Microsoft. It runs profile-driven performance benchmarks, stress tests, and qualification workloads on systems (particularly Azure VMs), collecting structured metrics. Supports Windows and Linux
microsoft/copilot-for-eclipse/.github/copilot-instructions.md
Checkstyle compliance (Google Java Style with custom rules): ```shell .\mvnw checkstyle:check ``` 3. **RUN** tests before submitting changes: ```shell .\mvnw test ``` 4. **FIX** all compilation errors, Checkstyle violations, and test
n1byn1kt/apitap/.github/copilot-instructions.md
Copilot Instructions for ApiTap ## Build and test commands - Install deps: `npm install` - Full test suite: `npm test` (Node test runner via `node --import tsx --test 'test/**/*.test.ts'`) - Single test file
microsoft-foundry/foundry-agent-webapp/.github/copilot-instructions.md
Gate** | `preToolUse` | Blocks direct `git commit`. Follow `committing-code` skill → commit via `-F COMMIT_MESSAGE.md`. | | **Test Reminder** | `preToolUse` | Advisory: reminds to run tests if test files exist for staged changes
Azure/autorest.powershell/.github/copilot-instructions.md
seconds. NEVER CANCEL. - Build all projects: `rush rebuild` -- takes 8 seconds. NEVER CANCEL. ### Testing and Validation - Run unit tests: `cd powershell && npm test` -- takes 1 second. Should show 3 passing
bartstc/vite-ts-react-template/.github/instructions/copilot-instructions.md
React 19, Vite 8, React Router 8, TanStack Query, Zustand, XState, Chakra UI, i18next. Testing: Vitest, Storybook, Playwright, MSW. ## Commands - `pnpm dev` — start dev server (port 5173) - `pnpm lint
hashicorp/copywrite/.github/copilot-instructions.md
Structure" section). - **Size:** small-to-medium repo, a handful of top-level packages. ## Build, test, lint, run (validated against CI) There is **no Makefile and no bootstrap script**. Use standard
microsoft/physical-ai-toolchain/.github/copilot-instructions.md
Required general instructions for entire codebase and project
aws/aws-parallelcluster-cookbook/cookbooks/line/.github/copilot-instructions.md
supports various OS platforms (check metadata.rb, kitchen.yml and .github/workflows/ci.yml for which platforms to specifically test) ## Project Structure **Critical Paths:** - `recipes/` - Chef recipes for cookbook functionality (if this is a recipe
aws/aws-parallelcluster-cookbook/cookbooks/yum/.github/copilot-instructions.md
supports various OS platforms (check metadata.rb, kitchen.yml and .github/workflows/ci.yml for which platforms to specifically test) ## Project Structure **Critical Paths:** - `recipes/` - Chef recipes for cookbook functionality (if this is a recipe
nambok/mentedb/.github/copilot-instructions.md
tool adapter ``` The SDKs are excluded from the Cargo workspace and build independently. ## Build, test, and lint Always run these before committing: ```bash cargo fmt --all cargo clippy --workspace
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.