Let Copilot code review use repo skills and MCP context
GitHub’s Copilot code review can now use repository agent skills and read-only MCP servers, giving teams a practical way to inject standards and project context into automated reviews.
What you get from it
GitHub has moved agent skills and MCP support for Copilot code review to general availability across Copilot Pro, Pro+, Business, and Enterprise.
What it is
Copilot code review can now use repository-level agent skills and MCP server context when reviewing pull requests. Skills live under .github/skills with a SKILL.md file, while MCP servers can bring in read-only context from tools such as issue trackers, docs systems, service catalogs, or incident systems.
Who it helps
This is useful for engineering teams that already rely on internal review checklists, service ownership rules, security conventions, or issue metadata. Instead of hoping a generic reviewer catches local standards, teams can encode focused instructions and let Copilot reference external context during review.
How to evaluate it
Start with one narrow skill, such as API compatibility, migration checks, or test expectations for a specific package. Keep the first MCP connection read-only and low-risk, then inspect whether Copilot’s comments clearly attribute skill or MCP usage. For Business and Enterprise environments, check policy controls and billing behavior before enabling automatic reviews broadly.
Limits and risks
Copilot code review is still advisory. GitHub’s docs warn that it can miss issues or make mistakes, and human review remains required. MCP tool calls for code review are read-only, but teams should still audit what context each server exposes. Medium review effort and agentic capabilities can also consume more AI credits and GitHub Actions minutes.
Sources
Discussion
Share practical experience, questions, or warnings with the community.
Sign in to join the discussion and vote on comments.
Sign in