Autonomous Coding Instructions
You are an autonomous coding agent.
## Read First
- PRD.md
- PROGRESS.md
- README.md
- AGENTS.md
- tests
- project/package files
## Work Loop
1. Pick the next incomplete task.
2. Implement the smallest
artifact — a plugin distribution
layout (`.claude-plugin/plugin.json` + `commands/` + `skills/`)
consumed directly by Claude Code, Copilot, Cursor, and Windsurf, with
no compilation, bundling, or packaging. The one build step
solved. Don't go into the specifics of the
code unless it adds clarity.
- Always add `ArthurClune` as reviewer.
- NEVER ever mention a `co-authored-by` or similar aspects
Agent Prime — Copilot System Instructions
> This file is auto-injected into every VS Code Copilot Chat session. It eliminates cold starts and makes the LLM aware of the full system
pull requests that modify `SKILL.md` files, apply the following
standards. Flag violations as inline codereview comments on the relevant lines.
---
## Critical: Agent Neutrality
Skills must be platform-agnostic. Flag
review your own work.** Independent means a different *machine*, not a
different session — co-located agents share one node key (#136).
- Verify claims against code. Reproduce; do not trust
toolkit as GitHub Copilot **Agent Skills** in `.github/skills/`. Copilot discovers them automatically (coding agent, codereview, Copilot CLI, agent mode in VS Code, and JetBrains agent mode in public preview
status across ALL checks is mandatory before marking any PR as ready for review. This ensures code quality, security, and prevents breaking changes from being merged
Copilot CodeReview Priorities
When reviewingcode in this repository, optimize for signal, not coverage.
## Review threshold
- Only leave a comment when you find a plausible behavioral defect, operational risk
Copilot codereview instructions for mcp-stdio
## Repository overview
`mcp-stdio` is a **stdio-to-HTTP/SSE gateway/relay** for the Model Context
Protocol. It translates between the stdio JSON
existing whole-repository debt from issues introduced by this PR.
Include the `ECorp code-review` label and reviewed head SHA in the summary so
maintainers can verify that this workflow
utilities that already exist is a common review finding. When the work spans multiple modules, scan for prior art first.
## Basic C# code style hints
### Layout
- `using` statements go inside
/login` | POST | Start GitHub device code OAuth flow |
| `/login/poll` | POST | Poll for completed device code auth |
| `/login/status` | GET | Check current auth state |
| `/models` | GET | List available models |
| `/models/set` | POST | Change