Using GitHub Copilot code review

Copilot code review is also available for organization members without a Copilot license, when enabled by an enterprise administrator or organization owner. See Copilot code review for organization members without a Copilot license.

Using Copilot code review

These instructions explain how to use Copilot code review in the GitHub website. To see instructions for other popular coding environments, click the appropriate tab at the top of the page.

1. On GitHub.com, create a pull request or navigate to an existing pull request.

2. Under "Reviewers" in the right sidebar, next to Copilot, click Request.

   

3. Wait for Copilot to review your pull request. This usually takes less than 30 seconds.

4. Scroll down and read through Copilot's comments.

   

   Copilot labels each comment with a severity level of "High," "Medium," or "Low" to help you prioritize the issues it finds based on their importance.

   By default, Copilot leaves a "Comment" review, not an "Approve" review or a "Request changes" review. This means that, by default, Copilot's reviews do not count toward required approvals for the pull request. However, if configured to do so, Copilot can leave "Approve" reviews. For more information, see Pull request approvals from Copilot.

5. Where possible, Copilot's feedback includes suggested changes which you can apply with a couple of clicks.

   If you're happy with the changes, you can accept a single suggestion from Copilot and commit it, or accept a group of suggestions together in a single commit. For more information, see Incorporar comentarios en tu solicitud de extracción.

   You can also invoke Copilot cloud agent to implement suggested changes. To do this, you must:

   • Enable GitHub Copilot code review and Copilot cloud agent.
   • On review comments from GitHub Copilot code review, click Fix with Copilot. This creates a draft comment on the pull request, where you can instruct Copilot to address specific feedback. You can then select whether Copilot will create a new pull request against your branch or a commit to the same pull request with the suggestions applied.

6. Copilot's review comments behave like review comments from humans. You can add reactions to them, comment on them, resolve them and hide them.

   Any comments you add to Copilot's review comments will be visible to humans, but they won't be visible to Copilot, and Copilot won't reply.

You can also request a review from Copilot through the GitHub REST API by requesting copilot-pull-request-reviewer[bot] as a reviewer. For more information, see Puntos de conexión de la API de REST para las solicitudes de revisión.

Enabling automatic reviews

By default, you manually request a review from Copilot on each pull request, in the same way you would request a review from a human. However, you can set up Copilot to automatically review all pull requests. See Configuración de la revisión de código mediante GitHub Copilot.

Requesting a re-review from Copilot

When you push changes to a pull request that Copilot has reviewed, it won't automatically re-review your changes unless you've configured it to review new pushes after enabling automatic reviews.

To manually request a re-review from Copilot, click the button next to Copilot's name in the Reviewers menu. For more information, see Solicitar una revisión de solicitud de extracción.

To automatically request re-reviews from Copilot on every push, enable automatic code review for the repository and select Review new pushes in the ruleset settings. For more information, see Configuración de la revisión de código mediante GitHub Copilot.

Choosing a review effort level

With review effort levels, you can choose the level of thoroughness of Copilot's review that matches the criticality of your code.

• Lite: Cost-efficient review that provides targeted feedback on glaring issues such as bugs, security vulnerabilities, and style inconsistencies.
• Balanced: Deeper analysis of complex logic, security-sensitive code, and cross-service changes, using a higher-reasoning model.

You can select Copilot review effort in the pull request before you request a review from Copilot, under the Reviewers section where Copilot appears as a reviewer. You can also set a default Copilot review effort in your settings. Organization owners and repository administrators can set a default Copilot review effort for automatic reviews.

For more information, see Sobre la revisión de código de GitHub Copilot.

Pull request approvals from Copilot

Every Copilot code review includes an approval assessment in the overview comment, indicating whether Copilot considers the pull request ready to approve. On its own, this assessment does not count toward merge requirements.

When approvals are enabled, Copilot can submit an approving review that satisfies your repository's required-approval rule the same way a teammate's approval would. If new commits are pushed after Copilot approves, the approval is dismissed, and you can re-request a review. For more details on required reviews, see Aprobación de una pull request con revisiones requeridas.

Approvals are off by default and can be configured at the enterprise, organization, and repository levels. Repository administrators can also use file paths to control which Copilot approvals count toward merge requirements. For configuration steps, see Configuración de la revisión de código mediante GitHub Copilot.

Customizing Copilot's reviews with custom instructions

Puede personalizar Copilot code review agregando instrucciones personalizadas al repositorio. Las instrucciones personalizadas del repositorio pueden ser específicas de todo el repositorio o de una ruta de acceso.

Use .github/copilot-instructions.md para obtener instrucciones de revisión para todo el repositorio que se deben aplicar en todo el código base. Este es un buen lugar para describir las expectativas de toda la organización, como los estándares de codificación, los criterios de revisión o las prácticas generales que Copilot deben tener en cuenta en cada revisión.

Use un AGENTS.md archivo en la raíz del repositorio para proporcionar contexto de repositorio adicional que ayude a Copilot comprender mejor cómo funciona el proyecto. Por ejemplo, puede explicar qué patrones son intencionales, qué partes del código base necesitan un examen más detallado y lo que el equipo considera una buena arquitectura, pruebas e prácticas de implementación. Esto ayuda a hacer que las revisiones sean más relevantes y alineadas con la forma en que el equipo compila software.

Utiliza archivos .github/instructions/**/*.instructions.md para instrucciones específicas para una ruta que solo se aplican al revisar los archivos correspondientes. Esto resulta útil cuando diferentes partes del repositorio siguen convenciones diferentes, requieren comprobaciones especializadas o necesitan instrucciones de revisión adaptadas a un lenguaje, marco o subsistema concretos.

Copilot code review también lee instrucciones personalizadas de los archivos CLAUDE.md, GEMINI.md y REVIEW.md de tu repositorio, si existen.

Para más información, consulta Agregar instrucciones personalizadas del repositorio para GitHub Copilot.

Ejemplo

Este ejemplo de un .github/copilot-instructions.md archivo contiene tres instrucciones que se aplicarán a todos los Copilot code reviewelementos del repositorio.

When performing a code review, respond in Spanish.

When performing a code review, apply the checks in the `/security/security-checklist.md` file.

When performing a code review, focus on readability and avoid nested ternary operators.

MCP servers and agent skills

Copilot code review can use agent skills and MCP servers configured in the repository, when they are relevant to the code being reviewed.

To make these available for Copilot code review on GitHub, configure:

• Agent skills in your repository (in .github/skills). If you want a skill to target review tasks, use a review-focused skill directory name such as code-review. For setup details, see Agregar aptitudes de agente para GitHub Copilot.
• MCP servers in repository Copilot settings. The GitHub MCP server and Playwright MCP server are enabled by default. For setup details, see Configuración de servidores MCP para el repositorio.

Copilot code review es más probable que use este contexto cuando:

• Los directorios de aptitudes del agente tienen nombres y descripciones centrados en la revisión, como code-review, que indican que están pensados para la revisión de solicitudes de incorporación de cambios.
• Las habilidades del agente o las instrucciones personalizadas le indican explícitamente a Copilot code review que use un contexto de MCP específico.
• Las descripciones de solicitudes de incorporación de cambios hacen referencia a los elementos disponibles a través de servidores MCP configurados, como claves de emisión o identificadores de incidente.

Para comprobar qué contexto Copilot code review de MCP se usa para una revisión específica, compruebe si hay atribución en la parte inferior de cada comentario de revisión. Estas atribución hacen referencia a la aptitud específica del agente o al servidor MCP que Copilot code review se usa para generar ese comentario. También puede abrir la sesión de revisión vinculada desde la escala de tiempo de la solicitud de incorporación de cambios y, a continuación, comprobar los registros de sesión para ver qué servidores y herramientas de MCP se llamaron.

En la configuración del repositorio, Allow Copilot usar herramientas de MCP al revisar las solicitudes de incorporación de cambios está habilitada de forma predeterminada. Deshabilite esta configuración si desea que los servidores MCP estén disponibles solo para Copilot cloud agenty no para Copilot code review. Para obtener instrucciones paso a paso, consulte Configuración de servidores MCP para el repositorio.

Customizing Copilot code review's environment

Copilot code review runs in an ephemeral development environment, similar to Copilot cloud agent. You can customize this environment using a GitHub Actions workflow file, in the same way you would for Copilot cloud agent, for example, to preinstall tools or dependencies, or to switch to a different operating system. For more information on how to structure this file, see Configuración del entorno de desarrollo.

You can use either of the following files to configure Copilot code review's environment:

• .github/workflows/copilot-setup-steps.yml: If you have already configured this file for Copilot cloud agent, Copilot code review will use the same configuration by default.
• .github/workflows/copilot-code-review.yml: We recommend creating this file if you want to configure Copilot code review's environment independently of Copilot cloud agent. If this file is present in your repository, it is used for Copilot code review instead of copilot-setup-steps.yml.

You can also configure firewall rules to control the domains and URLs that Copilot code review can access, at both the organization and repository level. These settings are configured separately from Copilot cloud agent's firewall settings, in their own section of the same "Internet access" tab. See Personalización o deshabilitación del firewall para GitHub Copilot.

Providing feedback on Copilot's reviews

You can provide feedback on Copilot's comments directly within each comment. We use this information to improve the product and the quality of Copilot's suggestions.

To provide feedback on a review comment from Copilot, click the thumbs up (👍) or thumbs down (👎) button.

When performing a code review, respond in Spanish.

When performing a code review, apply the checks in the `/security/security-checklist.md` file.

When performing a code review, focus on readability and avoid nested ternary operators.

gh pr create --reviewer @copilot

gh pr create --reviewer @copilot

? Reviewers  [Use arrows to move, space to select, <right> to all, <left> to none, type to filter]
  [ ]  Search (7472 more)
  [x]  monalisa (Mona Lisa)
> [x]  Copilot (AI)

gh pr edit PR-NUMBER --add-reviewer @copilot

gh pr edit PR-NUMBER --add-reviewer @copilot