From b92ec80ed43696315b79d8cc4c6940bfa929719e Mon Sep 17 00:00:00 2001 From: fernanduandrade Date: Thu, 30 Jul 2026 07:31:44 -0300 Subject: [PATCH 1/4] docs: adicionar template de pull request --- .github/pull_request_template.md | 66 ++++++++++++++++++++++++++++++++ 1 file changed, 66 insertions(+) create mode 100644 .github/pull_request_template.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 00000000..280e580f --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,66 @@ +## Summary + + + +### Alterações + + + +- ... +- ... +- ... + +--- + +## Plano de Testes + + + +- [ ] ... +- [ ] ... +- [ ] ... +- [ ] ... + +--- + +## Evidências + + + +### Antes + + + +### Depois + + + +--- + +## Issues Relacionadas + + + +Closes # From 65781a79a08119e4ffeb54a3ecff86bafe91e5d9 Mon Sep 17 00:00:00 2001 From: fernanduandrade Date: Mon, 3 Aug 2026 14:33:20 -0300 Subject: [PATCH 2/4] feat: incluir steps de quality gate no test plan --- .github/pull_request_template.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 280e580f..52b94f3e 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -1,4 +1,4 @@ -## Summary +## Contexto -- [ ] ... +- [ ] Executar `make check` +- [ ] Executar `make test` - [ ] ... - [ ] ... - [ ] ... @@ -61,6 +62,6 @@ Closes #123 Fixes #123 Resolves #123 Related to #123 ---> -Closes # +Exemplo: Closes #123 +--> From 44fe06782d9a8702f8ff36b4e1c71402679a5e7e Mon Sep 17 00:00:00 2001 From: fernanduandrade Date: Mon, 3 Aug 2026 14:38:15 -0300 Subject: [PATCH 3/4] feat: adicionar template pr para agentes de IA --- .../workflow/05-pull-requests.blade.php | 23 +++++++++++++++++++ 1 file changed, 23 insertions(+) create mode 100644 .ai/guidelines/workflow/05-pull-requests.blade.php diff --git a/.ai/guidelines/workflow/05-pull-requests.blade.php b/.ai/guidelines/workflow/05-pull-requests.blade.php new file mode 100644 index 00000000..698f198f --- /dev/null +++ b/.ai/guidelines/workflow/05-pull-requests.blade.php @@ -0,0 +1,23 @@ +@php +/** @var \Laravel\Boost\Install\GuidelineAssist $assist */ +@endphp + +# Pull Requests + +When creating or updating a GitHub pull request, agents MUST use the repository PR template at `.github/pull_request_template.md` as the source of truth for the PR body. + +## Required behavior + +- Fill the PR body using the template sections: `Contexto`, `Alterações`, `Plano de Testes`, `Evidências` and `Issues Relacionadas`. +- Preserve the template structure and headings instead of writing a free-form PR description. +- Populate the checklist in `Plano de Testes` with the validation steps that were actually run. +- Include the relevant validation commands from the project workflow, especially `make check` and `make test`, when applicable. +- Add issue references in the `Issues Relacionadas` section using the repository's expected format (for example: `Closes #123`). +- If the change has no visible UI impact, keep the `Evidências` section concise or leave it empty rather than inventing screenshots. + +## Expectations for agents + +- Do not create a PR body from scratch when the template exists. +- Adapt the template content to the specific change, but do not remove required sections unless the repository template already says they are optional. +- Prefer clear, concise Portuguese when the repository and existing templates are written in Portuguese. +- If the PR is for a change that affects behavior, include enough detail for reviewers to understand the impact, the validation performed, and the related issues. From c57cf89b978d435519be3768b55ac6170b7c8568 Mon Sep 17 00:00:00 2001 From: fernanduandrade Date: Mon, 3 Aug 2026 15:15:12 -0300 Subject: [PATCH 4/4] =?UTF-8?q?fix:=20ajutar=20guideline=20para=20n=C3=A3o?= =?UTF-8?q?=20ser=20um=20requisito=20obrig=C3=A1torio=20seguir=20o=20model?= =?UTF-8?q?o=20da=20PR?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../workflow/05-pull-requests.blade.php | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/.ai/guidelines/workflow/05-pull-requests.blade.php b/.ai/guidelines/workflow/05-pull-requests.blade.php index 698f198f..12fd4a9b 100644 --- a/.ai/guidelines/workflow/05-pull-requests.blade.php +++ b/.ai/guidelines/workflow/05-pull-requests.blade.php @@ -4,20 +4,18 @@ # Pull Requests -When creating or updating a GitHub pull request, agents MUST use the repository PR template at `.github/pull_request_template.md` as the source of truth for the PR body. +When creating or updating a GitHub pull request, agents should consider the repository PR template at `.github/pull_request_template.md` as a helpful reference for structuring the PR body. -## Required behavior +## Guidance -- Fill the PR body using the template sections: `Contexto`, `Alterações`, `Plano de Testes`, `Evidências` and `Issues Relacionadas`. -- Preserve the template structure and headings instead of writing a free-form PR description. -- Populate the checklist in `Plano de Testes` with the validation steps that were actually run. -- Include the relevant validation commands from the project workflow, especially `make check` and `make test`, when applicable. -- Add issue references in the `Issues Relacionadas` section using the repository's expected format (for example: `Closes #123`). +- Prefer using the template sections `Contexto`, `Alterações`, `Plano de Testes`, `Evidências` and `Issues Relacionadas` when they fit the change. +- Keep the structure clear and review-friendly, rather than writing a completely free-form PR description. +- Populate the checklist in `Plano de Testes` with the validation steps that were actually run, including relevant commands such as `make check` and `make test` when applicable. +- Add issue references in the `Issues Relacionadas` section using the repository's expected format (for example: `Closes #123`) when there is a related issue to link. - If the change has no visible UI impact, keep the `Evidências` section concise or leave it empty rather than inventing screenshots. ## Expectations for agents -- Do not create a PR body from scratch when the template exists. -- Adapt the template content to the specific change, but do not remove required sections unless the repository template already says they are optional. -- Prefer clear, concise Portuguese when the repository and existing templates are written in Portuguese. +- It is fine to draft a PR body without the template; the absence of the template does not block the PR. +- Adapt the content to the specific change and prefer clear, concise Portuguese when the repository and existing templates are written in Portuguese. - If the PR is for a change that affects behavior, include enough detail for reviewers to understand the impact, the validation performed, and the related issues.