simorgh
bbc/simorgh/.github/copilot-instructions.md
General guide for Simorgh
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
bbc/simorgh/.github/copilot-instructions.md
General guide for Simorgh
dragonflyoss/nydus/.github/copilot-instructions.md
blob_size, user_io); let blob_device = factory.get_device(&blob_info)?; blob_device.read(&mut bio)?; ``` ## Documentation Standards ### Code Documentation - Document all public APIs with `///` comments - Include examples in documentation - Document safety
AvdLee/Swift-Concurrency-Agent-Skill/.github/copilot-instructions.md
Security Considerations** - Scripts should be reviewed for security implications - External dependencies should be clearly documented - No malicious patterns (unexpected network calls, unauthorized file access) ### Common Issues to Flag - **Missing
Steady6 mentions in 2 weeks
No other project uses it yet
userdocs/qbittorrent-nox-static/.github/copilot-instructions.md
then it should be verbose enough to help. ## Astro and Astro starlight template for documentation - Always use the mcp server https://mcp.docs.astro.build/mcp - Always make sure imported mdx components start
streetsidesoftware/vscode-spell-checker/.github/copilot-instructions.md
name and type. Settings doc comments in `packages/_server/src/config/cspellConfig/` are the exception: they are user documentation
bitxeno/atvloadly/.github/copilot-instructions.md
internal/i18n/locales/](internal/i18n/locales/) - User language preference synced via `/api/lang/sync` ### Comments - **Mandatory**: All code comments and documentation MUST be written in English, even if the user asks in another language. ## Key Integration
nohajc/anylinuxfs/.github/instructions/copilot-instructions.md
plans, writing code, selecting APIs, or generating examples — it MUST resolve and fetch authoritative documentation via the Context7 MCP server before relying on its internal training knowledge. Treat these rules
feiskyer/claude-code-settings/.github/copilot-instructions.md
file with YAML frontmatter containing `name` and `description` fields. The description serves as both documentation and trigger condition. ### Skill File Structure All skill files must include YAML frontmatter: ```yaml --- name
No other project uses it yet
github/codeql-action/.github/copilot-instructions.md
internally. ## Review instructions - Prioritise identifying critical issues, such as logic bugs, over comments on documentation or typos. - When wording review comments, be helpful and friendly. Assume that the PR author
No other project uses it yet
collinbarrett/FilterLists/.github/copilot-instructions.md
search to gather comprehensive information about the filter list(s) 3. **Consult documentation**: Reference the FilterLists wiki for all supported properties: https://github.com/collinbarrett/FilterLists/wiki ### Data Model Population Strategy **Objective**: Fill
NuGet/NuGetGallery/.github/copilot-instructions.md
Contributions Changes target the `dev` branch and should be linked to an issue. Repository documentation contains multiple historical branch-name examples, so follow the current maintainer/issue convention rather than assuming
wiresock/proxifyre/.github/copilot-instructions.md
that can restore WiX 6.0.2. - If you are in a Linux environment: **Document that builds cannot be completed** and focus on repository navigation and structure analysis only. ### Build Prerequisites (Windows
MicrosoftDocs/cpp-docs/.github/copilot-instructions.md
Copilot Instructions for `cpp-docs-pr` ## Introduction This document contains general and repository-specific instructions for GitHub Copilot when assisting with the `cpp-docs-pr` repository. ## Priority Levels This document
IntersectMBO/plutus/.github/copilot-instructions.md
dependencies - Cabal build tool - Haskell Language Server (HLS) - Pre-commit hooks and formatting tools - Documentation build tools ## Building the Project ### Essential Pre-Build Steps ```bash # Always run these before building
Steady2 mentions in 2 weeks
No other project uses it yet
tokens-studio/figma-plugin/.github/copilot-instructions.md
monorepo managed with Yarn workspaces: - `packages/tokens-studio-for-figma` - Main Figma plugin package - `developer-knowledgebase` - Technical documentation ### Figma Plugin Architecture As a Figma plugin, our codebase is split into two main environments
amd/gaia/.github/copilot-instructions.md
Read back your changes and check for contradictions between docs, code, tests, and examples. ## Documentation rules - User-visible or public-surface changes must update the docs that describe them
Steady5 mentions in 2 weeks
No other project uses it yet
UbiquitousLearning/mllm/.github/copilot-instructions.md
codes or raise exceptions. - Validate inputs for public APIs and critical internal functions. c. Documentation: - Ensure public APIs, classes, and functions have clear docstrings or comments explaining purpose, parameters, returns
microsoft/hve-core/.github/copilot-instructions.md
Comprehensive coding guidelines and instructions for hve-core
mongodb/mongo-php-library/.github/copilot-instructions.md
security issues not mentioned in PR description - Breaking changes that weren't highlighted - Documentation that needs updating due to code changes ### What NOT to Comment On - Changes that are clearly
Steady5 mentions in 2 weeks
No other project uses it yet
microsoft/OpenAPI.NET/.github/copilot-instructions.md
body] [optional footer(s)] ``` ### Types - **feat**: A new feature - **fix**: A bug fix - **docs**: Documentation only changes - **style**: Changes that do not affect the meaning of the code (white-space
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.