{"meta":{"title":"Adding repository custom instructions for GitHub Copilot","intro":"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.","product":"GitHub Copilot","breadcrumbs":[{"href":"/ru/copilot","title":"GitHub Copilot"},{"href":"/ru/copilot/how-tos","title":"Инструкции"},{"href":"/ru/copilot/how-tos/copilot-on-github","title":"\n Copilot на GitHub"},{"href":"/ru/copilot/how-tos/copilot-on-github/customize-copilot","title":"Customize Copilot"},{"href":"/ru/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions","title":"Add custom instructions"},{"href":"/ru/copilot/how-tos/copilot-on-github/customize-copilot/add-custom-instructions/add-repository-instructions","title":"Add repository instructions"}],"documentType":"article"},"body":"# Adding repository custom instructions for GitHub Copilot\n\nCreate repository custom instructions files that give Copilot additional context on how to understand your project and how to build, test and validate its changes.\n\n## Introduction\n\nRepository 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](/ru/copilot/how-tos/configure-custom-instructions-in-your-ide/add-repository-instructions-in-your-ide). For more information about custom instructions, see [О кастомизации ответов GitHub Copilot](/ru/copilot/concepts/prompting/response-customization).\n\n## Предварительные требования для пользовательских инструкций репозитория\n\n* У вас должен быть пользовательский файл инструкций (см. приведенные ниже инструкции).\n\n* For Обзор кода 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.\n\n## Creating custom instructions\n\nCopilot on GitHub supports three types of repository custom instructions. For details of which GitHub Copilot features support these types of instructions, see [О кастомизации ответов GitHub Copilot](/ru/copilot/concepts/prompting/response-customization?tool=webui#support-for-repository-custom-instructions).\n\n* **Repository-wide custom instructions** apply to all requests made in the context of a repository.\n\n 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).\n\n* **Path-specific custom instructions** apply to requests made in the context of files that match a specified path.\n\n 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).\n\n 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.\n\n* **Agent instructions** are used by AI agents.\n\n Вы можете создать один или несколько `AGENTS.md` файлов, хранящихся в любом месте репозитория. Когда Copilot работает, приоритет будет иметь ближайший `AGENTS.md` файл в дереве каталогов. Для получения дополнительной информации смотрите [репозиторий agentsmd/agents.md](https://github.com/agentsmd/agents.md).\n\n Alternatively, you can use a single `CLAUDE.md` or `GEMINI.md` file stored in the root of the repository.\n\n## Creating repository-wide custom instructions\n\nYou 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 Copilot облачный агент to generate one for you.\n\n### Asking Copilot облачный агент to generate a `copilot-instructions.md` file\n\n1. Go to the agents tab at [github.com/copilot/agents](https://github.com/copilot/agents?ref_product=copilot\\&ref_type=engagement\\&ref_style=text).\n\n 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.\n\n2. In the prompt field dropdown, select the repository you want Copilot to generate custom instructions for.\n\n3. Copy the following prompt and paste it into the prompt field, customizing it if needed:\n\n ```markdown copy\n 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.\n\n 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.\n\n \n - Reduce the likelihood of a cloud agent pull request getting rejected by the user due to\n generating code that fails the continuous integration build, fails a validation pipeline, or\n having misbehavior.\n - Minimize bash command and build failures.\n - 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.\n \n\n \n - Instructions must be no longer than 2 pages.\n - Instructions must not be task specific.\n \n\n \n\n 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:\n \n\n - A summary of what the repository does.\n - High level repository information, such as the size of the repo, the type of the project, the languages, frameworks, or target runtimes in use.\n \n\n Add information about how to build and validate changes so the agent does not need to search and find it each time.\n \n\n - 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.\n - Each command should be validated by running it to ensure that it works correctly as well as any preconditions and postconditions.\n - 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.\n - Run the tests and document the order of steps required to run the tests.\n - Make a change to the codebase. Document any unexpected build issues as well as the workarounds.\n - Document environment setup steps that seem optional but that you have validated are actually required.\n - Document the time required for commands that failed due to timing out.\n - When you find a sequence of commands that work for a particular purpose, document them in detail.\n - Use language to indicate when something should always be done. For example: \"always run npm install before building\".\n - Record any validation steps from documentation.\n \n\n List key facts about the layout and architecture of the codebase to help the agent find where to make changes with minimal searching.\n \n\n - A description of the major architectural elements of the project, including the relative paths to the main project files, the location\n of configuration files for linting, compilation, testing, and preferences.\n - A description of the checks run prior to check in, including any GitHub workflows, continuous integration builds, or other validation pipelines.\n - Document the steps so that the agent can replicate these itself.\n - Any explicit validation steps that the agent can consider to have further confidence in its changes.\n - Dependencies that aren't obvious from the layout or file structure.\n - 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\n 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.\n \n \n\n \n - Perform a comprehensive inventory of the codebase. Search for and view:\n - README.md, CONTRIBUTING.md, and all other documentation files.\n - Search the codebase for build steps and indications of workarounds like 'HACK', 'TODO', etc.\n - All scripts, particularly those pertaining to build and repo or environment setup.\n - All build and actions pipelines.\n - All project files.\n - All configuration and linting files.\n - For each file:\n - 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?\n - If yes:\n - Document the command or information in detail.\n - Explicitly indicate which commands work and which do not and the order in which commands should be run.\n - Document any errors encountered as well as the steps taken to workaround them.\n - Document any other steps or information that the agent can use to reduce time spent exploring or trying and failing to run bash commands.\n - 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.\n \n - Document any errors encountered as well as the steps taken to work-around them.\n\n ```\n\n4. Click **** or press Enter.\n\nCopilot 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.\n\n### Writing your own `copilot-instructions.md` file\n\n1. In the root of your repository, create a file named `.github/copilot-instructions.md`.\n\n Create the `.github` directory if it does not already exist.\n\n2. Add natural language instructions to the file, in Markdown format.\n\n 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.\n\n> \\[!TIP]\n> The first time you create a pull request in a given repository with Copilot облачный агент, Copilot will leave a comment with a link to automatically generate custom instructions for the repository.\n\n## Creating path-specific custom instructions\n\n> \\[!NOTE]\n> Currently, on GitHub.com, path-specific custom instructions are only supported for Copilot облачный агент and Обзор кода Copilot.\n\n1. Создайте каталог, `.github/instructions` если он еще не существует.\n\n2. По желанию создайте подкаталоги `.github/instructions` для организации ваших файлов инструкций.\n\n3. Создайте один или несколько `NAME.instructions.md` файлов, где `NAME` указывается назначение инструкций. Имя файла должно заканчиваться `.instructions.md`.\n\n4. В начале файла создайте блок frontmatter, содержащий ключевое `applyTo` слово. Используйте синтаксис glob, чтобы указать, к каким файлам или каталогам применяются инструкции.\n\n Например:\n\n ```markdown\n ---\n applyTo: \"app/models/**/*.rb\"\n ---\n ```\n\n Можно указать несколько шаблонов, разделив их запятыми. Например, чтобы применить инструкции ко всем файлам TypeScript в репозитории, можно использовать следующий блок frontmatter:\n\n ```markdown\n ---\n applyTo: \"**/*.ts,**/*.tsx\"\n ---\n ```\n\n Примеры Glob:\n\n * ```\n `*` - все будут совпадать со всеми файлами текущей директории.\n ```\n * ```\n `**` или `**/*` — все совпадут со всеми файлами во всех каталогах.\n ```\n * ```\n `*.py` - будет совпадать со всеми `.py` файлами текущей папки.\n ```\n * ```\n `**/*.py` - будет рекурсивно совпадать со всеми `.py` файлами во всех каталогах.\n ```\n * ```\n `src/*.py`- будет `.py` совпадать со всеми `src` файлами в каталоге. Например `src/foo.py` , и `src/bar.py`_нет_`src/foo/bar.py`.\n ```\n * ```\n `src/**/*.py` - будет рекурсивно совпадать со всеми `.py` файлами в `src` каталоге. Например, `src/foo.py`, `src/foo/bar.py`и `src/foo/bar/baz.py`.\n ```\n * ```\n `**/subdir/**/*.py` - будет рекурсивно совпадать со всеми `.py` файлами в любой `subdir` папке на любой глубине. Например, `subdir/foo.py`, `subdir/nested/bar.py`, `parent/subdir/baz.py`, и `deep/parent/subdir/nested/qux.py`, но _не_`foo.py` на пути, не содержащем каталога `subdir` .\n ```\n\n5. Опционально, чтобы предотвратить использование файла либо Copilot облачный агент одним из вариантов Обзор кода Copilot, добавьте `excludeAgent` ключевое слово в блок фронтматтера. Используйте либо или `\"code-review\"``\"cloud-agent\"`.\n\n Например, следующий файл будет читаться только .Copilot облачный агент\n\n ```markdown\n ---\n applyTo: \"**\"\n excludeAgent: \"code-review\"\n ---\n ```\n\n Если ключевое `excludeAgent` слово не включено в передний блок Matterblock, оба Обзор кода Copilot и Copilot облачный агент будут использовать ваши инструкции.\n\n6. Добавьте пользовательские инструкции на естественном языке с помощью формата Markdown. Пробелы между инструкциями игнорируются, поэтому инструкции могут быть написаны как один абзац, каждый из которых находится на новой строке или разделен пустыми строками для удобочитаемости.\n\n
\n\nВы успешно добавили в репозиторий пользовательский файл инструкций?\n\n```\n \n Данет\n```\n\n
\n\n## Пользуемые инструкции\n\nИнструкции в файлах доступны для использования Copilot сразу после сохранения файла(ов). Инструкции автоматически добавляются к запросам, которые вы отправляете в Copilot.\n\nIn 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.\n\nWhenever 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.\n\n![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)\n\nYou can click the reference to open the file.\n\n> \\[!NOTE]\n>\n> * К запросу, отправленному на Copilot, может применяться несколько типов пользовательских инструкций. Личные инструкции имеют высший приоритет. Далее идут инструкции по репозиторию, а затем приоритетом ставятся инструкции по организации последними. Однако все наборы соответствующих инструкций предоставляются для Copilot.\n> * По возможности старайтесь избегать противоречивых наборов инструкций. Если вас беспокоит качество отклика, вы можете временно отключить инструкции репозитория. См [. раздел AUTOTITLE](/ru/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot?tool=webui#enabling-or-disabling-repository-custom-instructions).\n\n## Enabling or disabling custom instructions for Обзор кода Copilot\n\nCustom instructions are enabled for Обзор кода 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.\n\n1. На GitHubперейдите на главную страницу репозитория.\n2. Под именем репозитория щелкните ** Settings**. Если вкладка \"Параметры\" не отображается, выберите **раскрывающееся меню ** и нажмите кнопку **\"Параметры**\".\n\n ![Снимок экрана: заголовок репозитория с вкладками. Вкладка \"Параметры\" выделена темно-оранжевым контуром.](/assets/images/help/repository/repo-actions-settings.png)\n3. In the \"Code & automation\" section of the sidebar, click ** Copilot**, then **Code review**.\n4. Toggle the “Use custom instructions when reviewing pull requests” option on or off.\n\n> \\[!NOTE]\n> При просмотре pull-запроса Copilot использует пользовательские инструкции в базовой ветви pull request. Например, если ваш pull-запрос стремится объединиться `my-feature-branch` с `main`, Copilot будет использовать пользовательские инструкции в `main`.\n\n## Further reading\n\n* [Поддержка различных типов пользовательских инструкций](/ru/copilot/reference/custom-instructions-support)\n* [Пользовательские инструкции](/ru/copilot/tutorials/customization-library/custom-instructions)—a curated collection of examples\n* [Использование пользовательских инструкций для разблокировки возможностей обзора кода Copilot](/ru/copilot/tutorials/use-custom-instructions)"}