The CI Lint job is a hard gate. Mirror it locally before git push and before producing any artifact (PR body, release note, audit report) that claims CI is green. The Lint job runs (see .github/workflows/ci.yml): 1. uv run --extra dev ruff check src/ tests/ 2. uv run --extra dev ruff format --check src/ tests/ 3. YAML I/O safety guard (rejects raw yaml.dump(..., handle) outside utils/yaml_io.py; mark approved exceptions with # yaml-io-exempt). 4. File length guardrail (no src/*/.py may exceed…
This file defines repository-wide defaults for Copilot behavior. It is always applied. When modifying code generation or writer/refiner logic, treat schema-derived values as untrusted and ensure literal-context sanitization at the emission site. Use language/literal-appropriate sanitizers from src/Kiota.Builder/Writers/StringExtensions.cs (and Dart convention helpers where applicable). For writer changes that emit schema-derived text into generated code, ensure hostile content is escaped and covered by regression tests in tests/Kiota.Builder.Tests/Writers/. Before finishing implementation work:
When reviewing a pull request, use the mcp-code-reviewer skill. In interactive IDE and CLI sessions, return draft findings for human approval before posting them. In GitHub Copilot Code Review, post qualified inline comments directly as a comment-only review. Keep the review read-only: never modify code or the branch, approve or request changes, resolve threads, or invoke an agent to implement changes. When reviewing PRs that add or modify MCP tools, cross-reference the pre-merge checklist and check the following repository-specific completeness…
Solution: Open WinUIGallery.slnx in Visual Studio 2022+. Set WinUIGallery as the startup project. Build configurations: Debug, Release, Preview, Stable, Store, Sideload, Debug-Unpackaged. Platforms: x86, x64, ARM64. This is a WinUI 3 / Windows App SDK gallery app that demonstrates controls, styles, and design patterns. It is a companion to the Fluent Design guidelines. Each control demo lives in its own folder under Samples/{UniqueId}/ (e.g., Samples/Button/, Samples/CheckBox/). The folder name must match the control's UniqueId from ControlInfoData.json — this convention is…
This repository contains the in-the-box tasks for Azure Pipelines and Team Foundation Server. These instructions will help you understand how to build, test, and deploy tasks effectively. This repo provides open examples of how Azure Pipelines tasks are written and can help you write custom tasks for upload to your account or server. Tasks are tool runners that know how to execute tools like MSBuild, VSTest, etc., handle return codes, process stdout/stderr, write timeline records, and access credentials for Azure…
When reviewing pull requests in this repository, always check whether docs/ReleaseNotes.md should be updated. Use the release note policy in CONTRIBUTING.md ("Release Notes") as the default: - Release notes are…
This project brings eBPF (extended Berkeley Packet Filter) to Windows, enabling programmable OS kernel extensions for use cases like network filtering and observability. See docs/GettingStarted.md for prerequisites, build options, and detailed setup. See docs/AutomatedTests.md for test categories and descriptions.
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines. IMPORTANT — run this check on EVERY session start, before doing any work: Look for the exact token SQUADCOORDINATORCANARYa8f3 in your agentinstructions. This token is placed at the end of squad.agent.md. If it is missing, the coordinator file is missing or truncated. When the token is missing, you MUST: 1. STOP — do not proceed with standard Squad behavior.…
Agent Skills is a repository of skills, prompts, and MCP configurations for AI coding agents working with Azure SDKs and Microsoft AI Foundry services. Azure SDKs and Foundry APIs change constantly. Never work with stale knowledge. Before implementing anything with Azure/Foundry SDKs: If you skip this step and use outdated patterns, you will produce broken code. Apply these principles to every task. Don't assume. Don't hide confusion. Surface tradeoffs. Minimum code that solves the problem. Nothing speculative. The test: Would…
These instructions define how GitHub Copilot should assist with this project. The goal is to ensure consistent, high-quality code generation aligned with our conventions, stack, and best practices. - Code Style: The project uses an .editorconfig file to enforce coding standards. Follow the rules defined in .editorconfig for indentation, line endings, and other formatting. Additional information can be found on the wiki at Implementation. The library's public API requires C++11, and the project builds with C++17 (CMAKECXXSTANDARD 17). The command-line…
pg_durable is a PostgreSQL extension (pgrx/Rust) providing durable SQL function execution. Everything runs inside the PostgreSQL server—no external services. Two execution contexts: 1. Backend processes (user sessions): Build function graphs…
Clarity is an open-source TypeScript behavioral analytics library for tracking user interactions and session replays. Monorepo with Lerna/Yarn workspaces: Stack: TypeScript, Rollup, TSLint, Playwright, Lerna, Yarn workspaces Critical: clarity-js has two top priorities that must guide all development decisions: Rollup + TypeScript → multiple formats (CJS, ESM, IIFE minified). Build artifacts auto-cleaned to build/ or extension/ (gitignored). Build outputs per package: - clarity-js: clarity.js (CJS), clarity.module.js (ESM), clarity.min.js (minified), plus variants: clarity.extended.js, clarity.insight.js, clarity.performance.js, clarity.livechat.js, and dynamic agent builds (clarity.tidio.js,…
This repository contains a Rust-based, security-focused sandboxing library OS. To maintain high code quality and consistency, please adhere to the following guidelines when contributing.
Prefer .github/instructions/*.instructions.md files to capture durable architectural facts, conventions, and domain knowledge. Each file should have a description (for on-demand discovery) and optionally applyTo (for file-glob auto-attachment). Keep facts concise…