How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/PurviewIntegrations/.github/copilot-instructions.md
validate them in `src/validation/inputValidator.ts`. Set declared outputs via `core.setOutput`. - **Keep `action.yml`, the reader/writer code, and the docs in sync** when adding an input or output. Inputs/outputs use kebab-case. - **Keep
Poorgramer-ZackCopilot instructionsPoorgramer-Zack/dart-expert-skills/.github/copilot-instructions.md
guidance): Use when multiple approaches are valid or context determines the best approach. Example: code reviews. - **Medium freedom** (pseudocode/template with parameters): Use when a preferred pattern exists but variation
sbroenneCopilot instructionssbroenne/pytest-skill-engineering/.squad/copilot-instructions.md
starting work, check your capability profile in `.squad/team.md` under the **Coding Agent → Capabilities** section. - **🟢 Good fit** — proceed autonomously. - **🟡 Needs review** — proceed, but note in the PR description that a squad
shyamsridhar123Copilot instructionsshyamsridhar123/kevin-copilot/.github/copilot-instructions.md
structured implementation plan - `/ce-work` — Execute the plan with quality checks - `/ce-review` — Multi-agent code review - `/ce-compound` — Document solutions for future reference - `/lfg` — Full autonomous pipeline (plan → work → review) ## Documentation Structure
tarunccetCopilot instructionstarunccet/pm-skills/.github/copilot-instructions.md
when creating a value proposition or writing marketing copy. --- ## Vibe Coding (PM Builders) - **code-review-for-pms** — Review AI-generated code from a PM perspective: spec compliance, security, UX issues
edithatogoCopilot instructionsedithatogo/authentext/.github/copilot-instructions.md
implements a solution without clear reasoning. ## INSTRUCTION FOR TECHNICAL REVIEW 1. **Context Check:** Is this production code or a script? 2. **Safety Check:** Apply MISRA rules for Type Safety
MicrosoftCopilot instructionsmicrosoft/arc-switch/copilot-instructions.md
helping with this repository. ## Golang Best Practices ### Code Style and Organization - Follow the [Go Code Review Comments](https://github.com/golang/go/wiki/CodeReviewComments) for style guidance - Respect Go's [Effective Go](https://golang.org
mrcbrbn5361Copilot instructionsmrcbrbn5361/SyncytiumMD/.github/copilot-instructions.md
Instructions for SyncytiumMD ### 🤝 Live Handoff Status - **Active Agent:** `Antigravity` (Next: `Any`) - **Status:** `READY_FOR_REVIEW` - **Current Goal:** Release v0.2.0: correctness, security and extensibility release - **Pending Tasks:** - [ ] Run npm run release
qualcomm-linuxCopilot instructionsqualcomm-linux/qcom-linux-skills/.github/copilot-instructions.md
AGENTS.md](../AGENTS.md) — follow them for any change in this repository. The instructions below govern code review behavior only. ## Code review ### Comment discipline - Review only the lines this pull request adds
tasklessCopilot instructionstaskless/cli/.github/copilot-instructions.md
Copilot review instructions Repo-wide guidance for automated code review. Prioritize correctness and security over style. Be specific and actionable; cite the file and line. ## GitHub Actions — credential & secret safety
wesleysimplicioCopilot instructionswesleysimplicio/PiAPI-Skills/.github/copilot-instructions.md
Tools: `edit`, `terminal`, `search`. Aciona quando tarefa exige cobertura nova ou regression test. - **`reviewer.agent.md`** — Code Reviewer. Read-only. Comenta problemas e sugestões em PR. Tools: `search`, `read`. Aciona em revisão
dirnbauerCopilot instructionsdirnbauer/typo3-skills/.github/copilot-instructions.md
assert from memory. - Never edit a vendored skill — add `references/webconsulting-additions.md`. See VENDORED.md. - Always review AI-generated code before committing. ## Licence Code MIT · Content CC-BY-SA-4.0 · vendored skills retain
gcontiniCopilot instructionsgcontini/resumix/.github/copilot-instructions.md
attempts` rounds) → keyword highlight → render for good. Returns `(document, tex, pdf, summary)`. Pure library code — inputs in memory, outputs returned, nothing read from a configured path; progress leaves through
GktuOktayCopilot instructionsGktuOktay/ai-skills/.github/copilot-instructions.md
Dual-Validation & Data Integrity Gate (Auditor) You are an inflexible Quality Gate. You review all code written by Backend, Frontend, and Database Architects. If the code does not meet
Harmitx7Copilot instructionsHarmitx7/tribunal-kit/.github/copilot-instructions.md
penetration-tester` | | Database performance / slow queries | `db-latency-auditor` | | AI/LLM integration code / prompts | `ai-code-reviewer` | | System design / scale / capacity planning | `system-architect` | | Cloud infrastructure / AWS / Terraform / Docker
jbaruchCopilot instructionsjbaruch/agentic-context-registry/.github/copilot-instructions.md
Copilot code review — scope This repository is reviewed by a separate policy reviewer — the central `jbaruch/coding-policy` fleet reviewer (a scheduled GitHub App that reviews every PR against the installed `jbaruch/coding-policy
jyunmingCopilot instructionsjyunming/Axon/.github/copilot-instructions.md
code datasets by design. - **Do** set `code_graph: true` when ingesting a source code repository if you want cross-file link traversal at query time. - **Do** use `query_router: heuristic
koldovskyCopilot instructionskoldovsky/project-factory/.github/copilot-instructions.md
trajectory checks, tests) is identical across tools. Copilot lacks Claude Code's **parallel** subagent fan-out, so run the review-gate / eval / spec passes **sequentially with fresh context** — the agent
MicrosoftCopilot instructionsmicrosoft/aloop/.github/copilot-instructions.md
review/ sample-builder/ changelog-writer/ data-analysis/ doc-writer/ strategic-planning/ output/ # Local download target for artifacts ``` ## Key Conventions ### Naming - Project is always **aloop** (lowercase) in code, docs, CLI output
punt-labsCopilot instructionspunt-labs/quarry/.github/copilot-instructions.md
Copilot Code Review Instructions ## What to focus on - Logic errors, off-by-one, null/None paths, unhandled edge cases - Security: injection, credential exposure, path traversal, unsafe deserialization - API contract violations: function
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.
