> For the complete documentation index, see [llms.txt](https://help.aikido.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aikido.dev/docs/docs-ja/autofix-to/configure/pull-request-templates.md).

# プルリクエストテンプレート

AutoFix は、リポジトリ内のプルリクエストテンプレートを使用して、各プルリクエストの説明を生成します。サポートされているテンプレートが見つからない場合、AutoFix は既定のテンプレートを使用します。

AutoFix は、次のテンプレートの場所を確認します:

* `pull_request_template.md`
* `PULL_REQUEST_TEMPLATE.md`
* `pull_request_template.txt`
* `docs/pull_request_template.md`
* `docs/PULL_REQUEST_TEMPLATE.md`
* `docs/pull_request_template.txt`
* `.github/PULL_REQUEST_TEMPLATE.md`
* `.github/pull_request_template.md`
* `.gitlab/merge_request_templates/Default.md`
* `.azuredevops/pull_request_template.md`
* `.azuredevops/pull_request_template.txt`
* `.vsts/pull_request_template.md`
* `.vsts/pull_request_template.txt`

プルリクエストテンプレートの例:

{% code title="PULL\_REQUEST\_TEMPLATE.md" %}

```
# 概要

<!-- この PR は何をしますか? -->

# セキュリティへの影響

<!-- 修正するセキュリティ脆弱性と、それが重要である理由を説明してください -->

# 修正の詳細

<!-- 修正の技術的詳細 -->

# 警告

<!-- 修正に関する警告 -->

# 関連タスク

<!-- 関連するチケットや issue へのリンク -->

# チェックリスト

- [ ] 変更内容を確認した
- [ ] この修正でリグレッションが発生しないことを確認した
- [ ] マージを承認した
```

{% endcode %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.aikido.dev/docs/docs-ja/autofix-to/configure/pull-request-templates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.