Add support to copilot - #35
Conversation
26ea90b to
1736ca8
Compare
david-santos-os
left a comment
There was a problem hiding this comment.
Reviewed with focus on two things: (a) parity of copilot/skill.md with the existing Claude Code / Kiro / root skill docs, and (b) whether the README changes affect the docs for the existing harnesses.
Overall: solid addition. I diffed copilot/skill.md section-by-section against the other three skill docs: every shared section (intro, Tools at a glance, Caveats, Rules, Names, Answering, Mentor session round-trip, Context Service visibility, Workflows) is byte-identical, with only the harness-specific First use / setup and Authenticating sections diverging — exactly the intended shape. The README additions are pure insertions and the existing harness sections are untouched. The dual-key canonical copilot/mcp.json, with comments explaining which surface reads which key, is a nice single-source-of-truth touch.
Five pre-merge asks, each as an inline comment:
- Update
CLAUDE.md+CONTRIBUTING.mdfor the fourth lockstep doc — the most important one (anchored oncopilot/skill.mdbecause those files aren't in this diff). - Restore an updated "harnesses we test against" sentence in the README.
- Add the missing "retry the user's original request" step to the Copilot setup flow.
- MINOR version bump per the
CONTRIBUTING.mdpolicy (anchored on the README because.claude-plugin/*isn't in this diff). - A sweep of small nits (fence typo, step-4 wording, VS auth path, casing, trailing newline, stale PR description).
One thing I couldn't validate locally: the Copilot CLI syntax (copilot mcp add --transport http, /mcp reload, /mcp show) and the Visual Studio "Manage Authentication" CodeLens. GitHub iterates these surfaces quickly, so a quick confirmation in the PR that each of the three flows was run end-to-end on current versions would be great.
This PR is for adding Microsoft Copilot as a supported harness, alongside the existing Claude Code plugin and Kiro Power.
README.mdfor the three interactive surfaces — VS Code, Copilot CLI, and Visual Studio — in the same paste-into-your-assistant style as the Claude Code and Kiro sections.copilot/mcp.json— a single canonical config carrying both top-level keys:servers(VS Code + Visual Studio) andmcpServers(Copilot CLI). One source of truth the install prompts copy the matching key out of.copilot/skills.md— the conventions doc, adapted from rootSKILL.mdand structured like the Kiro steering file (intro → CopilotFirst use / setup→ full conventions body). Read automatically by VS Code, Visual Studio, the CLI (which also honorsAGENTS.md), and the cloud agent.