cli-continues
yigitkonur/cli-continues/.github/copilot-instructions.md
No summary in the file. Open it to read it.
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
yigitkonur/cli-continues/.github/copilot-instructions.md
No summary in the file. Open it to read it.
HexmosTech/git-lrc/.github/copilot-instructions.md
Build and install lrc locally with: make build-local && lrc hooks install When building the lrc command, always use the binary name "lrc" A primary rule in programming is that…
microsoft/pict/.github/copilot-instructions.md
Comprehensive instructions for developing in the PICT (Pairwise Independent Combinatorial Testing) repository PICT (Pairwise Independent Combinatorial Testing) is a Microsoft open-source command-line tool and C++ library for generating test cases…
microsoft/fluentui-react-native/.github/copilot-instructions.md
See AGENTS.md for guidance on working with code in this repository.
microsoft/fhir-server/.github/copilot-instructions.md
Core project guidelines, coding standards, and architecture principles are in AGENTS.md at the repo root — read it first. This file adds Copilot-specific skill activation routing and ADR guidance. Activate the relevant skill from .github/skills/ before any architecture task. When creating or updating an ADR in docs/arch/: - Use the create-adr skill. - Cover states, behaviors, outcomes, and edge cases thoroughly. - Reference prior ADRs and the FHIR specification. - If the decision obsoletes a prior ADR, update that ADR…
microsoft/mxc/.github/copilot-instructions.md
MXC (Microsoft eXecution Container) is a cross-platform sandboxed code execution system. Prefer precise, scoped changes and preserve existing platform behavior, feature gates, wire compatibility, and failure semantics. The Rust toolchain is pinned by src/rust-toolchain.toml. Run Rust commands from src/ or pass --manifest-path src/Cargo.toml. Prefer the smallest test command covering the change. Host-dependent backend suites live under tests/scripts/; use the applicable backend guide and docs/ci-validation-infrastructure.md before running or changing them. - Production parsing dispatches through exact closed contracts and their version-specific…
specstoryai/getspecstory/.github/copilot-instructions.md
Examine the file changes for the pull request. Ignore any changes to: - .specstory/history files - .claude files - ./specstory binary - CLAUDE.md - AGENT.md - changelog.md Please code review the pull request. Review line by line, pay attention to: In addition to the line by line review, suggest the 3 most important improvements for this code review. In addition to the 3 most important improvements, let's also think about if any of these changes could benefit from new, updated…
github/gh-skyline/.github/copilot-instructions.md
No summary in the file. Open it to read it.
sceneview/sceneview/.github/copilot-instructions.md
Open-source 3D & AR SDK for Android and iOS. AI-first design — optimized for LLM code generation. ModelNode, CubeNode, SphereNode, CylinderNode, PlaneNode, MeshNode, ImageNode, VideoNode, ViewNode, LightNode, DynamicSkyNode, FogNode, ReflectionProbeNode, LineNode, PathNode, BillboardNode, TextNode, PhysicsNode, AnchorNode, HitResultNode, AugmentedImageNode, AugmentedFaceNode, CloudAnchorNode, CapsuleNode, DepthMeshNode, PlacementReticleNode, TrackableNode For AI-assisted SceneView development:
microsoft/waza/.squad/copilot-instructions.md
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously, follow these guidelines. Before starting work on any issue: Before starting work, check your capability profile in .squad/team.md under the Coding Agent → Capabilities section. Use the squad branch convention: Example: squad/42-fix-login-validation When opening a PR: - Reference the issue: Closes #{issue-number} - If the issue had a squad:{member} label, mention the member: Working as {member} ({role}) - If this is a…
microsoft/waza/.squad/templates/copilot-instructions.md
You are working on a project that uses Squad, an AI team framework. When picking up issues autonomously or using Squad, follow these guidelines. IMPORTANT — run this check only when the session is expected to use Squad Coordinator behavior, before doing any Squad 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. Do not run this check for…
microsoft/gctoolkit/.github/copilot-instructions.md
No summary in the file. Open it to read it.
sipyourdrink-ltd/bernstein/.github/copilot-instructions.md
Bernstein is the open-source governance layer for AI agents (Python 3.12+), one git worktree per task. There is no model in the coordination loop - the orchestrator is deterministic Python, NOT an LLM - so the same plan replays to a byte-identical task graph. NEVER run uv run pytest tests/ - it leaks 100GB+ RAM. Always use scripts/run_tests.py.
supabase/supabase-swift/.github/copilot-instructions.md
@../AGENTS.md
GanyuanRan/Aegis/.github/copilot-instructions.md
This repository uses Aegis as method-pack workflow discipline. Before risky implementation, prefer the smallest relevant Aegis skill from .github/skills/ or the linked Aegis skill directories. Keep detailed workflow logic in the skill body rather than duplicating it here. Key repository boundaries: - treat Aegis as Aegis Method Pack (runtime-ready), not a runtime core - keep user instructions and target-project rules above Aegis guidance - do not claim authoritative GateDecision or final completion authority - require fresh verification evidence before completion…
datalayer/jupyter-mcp-server/.github/copilot-instructions.md
Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here. Jupyter MCP Server is a Python-based Model Context Protocol (MCP) server implementation that enables real-time interaction with Jupyter Notebooks. The project uses a modern Python build system with hatch, and includes comprehensive testing, linting, and documentation. NETWORK TIMEOUT WARNING: pip install commands may fail with SSL certificate errors or read timeouts when connecting to PyPI.…
microsoft/CSS-Exchange/.github/copilot-instructions.md
NEVER commit, push, or create PRs without explicit user instruction. NEVER auto-fix issues found during code review. Report findings only. NEVER present code as complete without running Invoke-CodeFormatterOnFiles and SpellCheck.ps1 first. ALWAYS report findings and wait for user decision before modifying the repository. ALWAYS commit only the specific files the user requests. No extra files. ALWAYS use named parameters instead of positional parameters. ALWAYS ensure .ps1 files have UTF-8 BOM encoding. When counting code patterns (function calls, occurrences), ALWAYS exclude…
microsoft/griffel/.github/copilot-instructions.md
Griffel is a CSS-in-JS library with near-zero runtime, SSR support, and ahead-of-time compilation. It's organized as a monorepo using Nx with 16+ packages and applications including React bindings, build-time transforms, and DevTools. Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here. CRITICAL: NEVER CANCEL long-running commands. Set timeouts appropriately. When using Nx affected commands in a repository that may not have a main branch…
AvdLee/Xcode-Build-Optimization-Agent-Skill/.github/copilot-instructions.md
Review changes as an Agent Skills expert and Xcode build optimization reviewer. Keep this repository focused on: Do not turn the repository into general iOS architecture guidance or product documentation. When reviewing changes, prioritize:
Azure/GPT-RAG/.github/copilot-instructions.md
This repository follows a structured workflow based on two primary branches: All work must follow the branching, versioning, and changelog rules defined below. Unless explicitly instructed otherwise: Examples: - feature/conversation-metadata - feature/improve-chat-history Examples: - release/1.2.3 - release/2.4.2 When preparing a release branch: - Update version references where applicable - Update CHANGELOG.md - Ensure the repository reflects a releasable state - Do NOT introduce new feature work - GitHub Release titles MUST be exactly the tag name (for example, v2.8.0). Never…
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.