# Adding repository custom instructions for GitHub Copilot Create repository custom instructions files that give Copilot additional context on how to understand your project and how to build, test and validate its changes. ## Introduction Repository custom instructions let you provide Copilot with repository-specific guidance and preferences on GitHub. To find out how to set up custom instructions in an IDE, see [Adding repository custom instructions for GitHub Copilot in your IDE](/es/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide). For more information about custom instructions, see [Acerca de la personalización de las respuestas de GitHub Copilot](/es/copilot/concepts/prompting/response-customization). ## Requisitos previos para las instrucciones personalizadas del repositorio * Debes tener un archivo de instrucciones personalizado (consulta las instrucciones a continuación). * For revisión de código Copilot, your personal choice of whether to use custom instructions must be set to enabled. This is enabled by default. See [Enabling or disabling repository custom instructions](#enabling-or-disabling-custom-instructions-for-copilot-code-review) later in this article. ## Creating custom instructions Copilot on GitHub supports three types of repository custom instructions. For details of which GitHub Copilot features support these types of instructions, see [Acerca de la personalización de las respuestas de GitHub Copilot](/es/copilot/concepts/prompting/response-customization?tool=webui#support-for-repository-custom-instructions). * **Repository-wide custom instructions** apply to all requests made in the context of a repository. These are specified in a `copilot-instructions.md` file in the `.github` directory of the repository. See [Creating repository-wide custom instructions](#creating-repository-wide-custom-instructions). * **Path-specific custom instructions** apply to requests made in the context of files that match a specified path. These are specified in one or more `NAME.instructions.md` files within or below the `.github/instructions` directory in the repository. See [Creating path-specific custom instructions](#creating-path-specific-custom-instructions). If the path you specify matches a file that Copilot is working on, and a repository-wide custom instructions file also exists, then the instructions from both files are used. * **Agent instructions** are used by AI agents. Puedes crear uno o más archivos `AGENTS.md`, almacenados en cualquier lugar del repositorio. Cuando Copilot funciona, el archivo más `AGENTS.md` cercano del árbol de directorios tendrá prioridad. Para obtener más información, consulte el [repositorio agentsmd/agents.md](https://github.com/agentsmd/agents.md). Alternatively, you can use a single `CLAUDE.md` or `GEMINI.md` file stored in the root of the repository. ## Creating repository-wide custom instructions You can create your own custom instructions file from scratch. See [Writing your own copilot-instructions.md file](#writing-your-own-copilot-instructionsmd-file). Alternatively, you can ask agente en la nube de Copilot to generate one for you. ### Asking agente en la nube de Copilot to generate a `copilot-instructions.md` file 1. Go to the agents tab at [github.com/copilot/agents](https://github.com/copilot/agents?ref_product=copilot\&ref_type=engagement\&ref_style=text). You can also reach this page by clicking the **** button next to the search bar on any page on GitHub, then selecting **Agents** from the sidebar. 2. In the prompt field dropdown, select the repository you want Copilot to generate custom instructions for. 3. Copy the following prompt and paste it into the prompt field, customizing it if needed: ```markdown copy Your task is to "onboard" this repository to Copilot cloud agent by adding a .github/copilot-instructions.md file in the repository that contains information describing how a cloud agent seeing it for the first time can work most efficiently. You will do this task only one time per repository and doing a good job can SIGNIFICANTLY improve the quality of the agent's work, so take your time, think carefully, and search thoroughly before writing the instructions. - Reduce the likelihood of a cloud agent pull request getting rejected by the user due to generating code that fails the continuous integration build, fails a validation pipeline, or having misbehavior. - Minimize bash command and build failures. - Allow the agent to complete its task more quickly by minimizing the need for exploration using grep, find, str_replace_editor, and code search tools. - Instructions must be no longer than 2 pages. - Instructions must not be task specific. Add the following high level details about the codebase to reduce the amount of searching the agent has to do to understand the codebase each time: - A summary of what the repository does. - High level repository information, such as the size of the repo, the type of the project, the languages, frameworks, or target runtimes in use. Add information about how to build and validate changes so the agent does not need to search and find it each time. - For each of bootstrap, build, test, run, lint, and any other scripted step, document the sequence of steps to take to run it successfully as well as the versions of any runtime or build tools used. - Each command should be validated by running it to ensure that it works correctly as well as any preconditions and postconditions. - Try cleaning the repo and environment and running commands in different orders and document errors and misbehavior observed as well as any steps used to mitigate the problem. - Run the tests and document the order of steps required to run the tests. - Make a change to the codebase. Document any unexpected build issues as well as the workarounds. - Document environment setup steps that seem optional but that you have validated are actually required. - Document the time required for commands that failed due to timing out. - When you find a sequence of commands that work for a particular purpose, document them in detail. - Use language to indicate when something should always be done. For example: "always run npm install before building". - Record any validation steps from documentation. List key facts about the layout and architecture of the codebase to help the agent find where to make changes with minimal searching. - A description of the major architectural elements of the project, including the relative paths to the main project files, the location of configuration files for linting, compilation, testing, and preferences. - A description of the checks run prior to check in, including any GitHub workflows, continuous integration builds, or other validation pipelines. - Document the steps so that the agent can replicate these itself. - Any explicit validation steps that the agent can consider to have further confidence in its changes. - Dependencies that aren't obvious from the layout or file structure. - Finally, fill in any remaining space with detailed lists of the following, in order of priority: the list of files in the repo root, the contents of the README, the contents of any key source files, the list of files in the next level down of directories, giving priority to the more structurally important and snippets of code from key source files, such as the one containing the main method. - Perform a comprehensive inventory of the codebase. Search for and view: - README.md, CONTRIBUTING.md, and all other documentation files. - Search the codebase for build steps and indications of workarounds like 'HACK', 'TODO', etc. - All scripts, particularly those pertaining to build and repo or environment setup. - All build and actions pipelines. - All project files. - All configuration and linting files. - For each file: - think: are the contents or the existence of the file information that the cloud agent will need to implement, build, test, validate, or demo a code change? - If yes: - Document the command or information in detail. - Explicitly indicate which commands work and which do not and the order in which commands should be run. - Document any errors encountered as well as the steps taken to workaround them. - Document any other steps or information that the agent can use to reduce time spent exploring or trying and failing to run bash commands. - Finally, explicitly instruct the agent to trust the instructions and only perform a search if the information in the instructions is incomplete or found to be in error. - Document any errors encountered as well as the steps taken to work-around them. ``` 4. Click **** or press Enter. Copilot will start a new session, which will appear in the list below the prompt box. Copilot will create a draft pull request, write your custom instructions, push them to the branch, then add you as a reviewer when finished, triggering a notification. ### Writing your own `copilot-instructions.md` file 1. In the root of your repository, create a file named `.github/copilot-instructions.md`. Create the `.github` directory if it does not already exist. 2. Add natural language instructions to the file, in Markdown format. Whitespace between instructions is ignored, so the instructions can be written as a single paragraph, each on a new line, or separated by blank lines for legibility. > \[!TIP] > The first time you create a pull request in a given repository with agente en la nube de Copilot, Copilot will leave a comment with a link to automatically generate custom instructions for the repository. ## Creating path-specific custom instructions > \[!NOTE] > Currently, on GitHub.com, path-specific custom instructions are only supported for agente en la nube de Copilot and revisión de código Copilot. 1. Crea el directorio `.github/instructions` si no existe todavía. 2. Opcionalmente, cree subdirectorios de `.github/instructions` para organizar sus archivos de instrucciones. 3. Crea uno o varios archivos `NAME.instructions.md`, donde `NAME` indica el propósito de las instrucciones. El nombre de archivo debe terminar con `.instructions.md`. 4. Al principio del archivo, crea un bloque de texto preliminar que contenga la palabra clave `applyTo`. Usa la sintaxis global para especificar a qué archivos o directorios se aplican las instrucciones. Por ejemplo: ```markdown --- applyTo: "app/models/**/*.rb" --- ``` Puedes especificar varios patrones si los separas con comas. Por ejemplo, para aplicar las instrucciones a todos los archivos TypeScript del repositorio, podrías usar el siguiente bloque de texto preliminar: ```markdown --- applyTo: "**/*.ts,**/*.tsx" --- ``` Ejemplos de Glob: * ``` `*` - coincidirá con todos los archivos del directorio actual. ``` * ``` `**` o `**/*` - coincidirán con todos los archivos en todos los directorios. ``` * ``` `*.py` : coincidirá con todos los `.py` archivos del directorio actual. ``` * ``` `**/*.py` : coincidirá recursivamente con todos los `.py` archivos de todos los directorios. ``` * ``` `src/*.py` : coincidirá con todos los `.py` archivos del `src` directorio. Por ejemplo, `src/foo.py` y `src/bar.py`_pero no_`src/foo/bar.py`. ``` * ``` `src/**/*.py` : coincidirá recursivamente con todos los `.py` archivos del `src` directorio. Por ejemplo, `src/foo.py`, `src/foo/bar.py` y `src/foo/bar/baz.py`. ``` * ``` `**/subdir/**/*.py` : coincidirá recursivamente con todos los `.py` archivos de cualquier `subdir` directorio a cualquier profundidad. Por ejemplo, `subdir/foo.py`, `subdir/nested/bar.py`, `parent/subdir/baz.py`y `deep/parent/subdir/nested/qux.py`, pero _no_`foo.py` en una ruta de acceso que no contiene un `subdir` directorio. ``` 5. De forma opcional, para evitar que el archivo sea usado por agente en la nube de Copilot o revisión de código Copilot, agregue la palabra clave `excludeAgent` al bloque frontmatter. Use `"code-review"` o `"cloud-agent"`. Por ejemplo, el archivo siguiente solo lo leerá agente en la nube de Copilot. ```markdown --- applyTo: "**" excludeAgent: "code-review" --- ``` Si la `excludeAgent` palabra clave no se incluye en el bloque de front matter, tanto revisión de código Copilot como agente en la nube de Copilot usarán tus instrucciones. 6. Agrega las instrucciones personalizadas en lenguaje natural mediante el formato Markdown. Se ignora el espacio en blanco entre las instrucciones, por lo que estas pueden escribirse como un solo párrafo, cada una en una nueva línea o separadas por líneas en blanco para mejorar la legibilidad.

¿Has agregado correctamente un archivo de instrucciones personalizado al repositorio? ``` Sí No ```

## Instrucciones personalizadas en uso Las instrucciones de los archivos están disponibles para su uso por Copilot tan pronto como guarde el/los archivo(s). Las instrucciones se agregan automáticamente a las solicitudes que envíe a Copilot. In Copilot Chat ([github.com/copilot](https://github.com/copilot)), you can start a conversation that uses repository custom instructions by adding, as an attachment, the repository that contains the instructions file. Whenever repository custom instructions are used by Copilot Chat, the instructions file is added as a reference for the response that's generated. To find out whether repository custom instructions were used, expand the list of references at the top of a chat response in the Chat panel and check whether the `.github/copilot-instructions.md` file is listed. ![Screenshot of an expanded References list, showing the 'copilot-instructions.md' file highlighted with a dark orange outline.](/assets/images/help/copilot/custom-instructions-ref-in-github.png) You can click the reference to open the file. > \[!NOTE] > > * Se pueden aplicar varios tipos de instrucciones personalizadas a una solicitud enviada a Copilot. Las instrucciones personales tienen la máxima prioridad. Las instrucciones del repositorio vienen a continuación y, a continuación, las instrucciones de la organización se priorizan en último lugar. Sin embargo, se proporcionan todos los conjuntos de instrucciones pertinentes a Copilot. > * Siempre que sea posible, intente evitar proporcionar conjuntos conflictivos de instrucciones. Si le preocupa la calidad de la respuesta, puede deshabilitar temporalmente las instrucciones del repositorio. Consulta [Adding repository custom instructions for GitHub Copilot](/es/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot?tool=webui#enabling-or-disabling-repository-custom-instructions). ## Enabling or disabling custom instructions for revisión de código Copilot Custom instructions are enabled for revisión de código Copilot by default but you can disable, or re-enable, them in the repository settings on GitHub.com. This applies to Copilot's use of custom instructions for all code reviews it performs in this repository. 1. En GitHub, navegue hasta la página principal del repositorio. 2. Debajo del nombre del repositorio, haz clic en ** Settings**. Si no puedes ver la pestaña "Configuración", selecciona el menú desplegable **** y, a continuación, haz clic en **Configuración**. ![Captura de pantalla de un encabezado de repositorio en el que se muestran las pestañas. La pestaña "Configuración" está resaltada con un contorno naranja oscuro.](/assets/images/help/repository/repo-actions-settings.png) 3. In the "Code & automation" section of the sidebar, click ** Copilot**, then **Code review**. 4. Toggle the “Use custom instructions when reviewing pull requests” option on or off. > \[!NOTE] > Al revisar una solicitud de incorporación de cambios, Copilot usa las instrucciones personalizadas de la rama base de la solicitud de incorporación de cambios. Por ejemplo, si la solicitud de incorporación de cambios busca combinar `my-feature-branch` en `main`, Copilot usará las instrucciones personalizadas de `main`. ## Further reading * [Compatibilidad con diferentes tipos de instrucciones personalizadas](/es/copilot/reference/custom-instructions-support) * [Instrucciones personalizadas](/es/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples * [Uso de instrucciones personalizadas para desbloquear la eficacia de la revisión de código de Copilot](/es/copilot/tutorials/use-custom-instructions)