chore(agents): add CONTRIBUTING.md compliance steps to agent-evolution-worker

ISSUES CLOSED: #8370
This commit is contained in:
2026-04-14 17:49:45 +00:00
committed by Forgejo
parent 92c3bd8732
commit c4122f877a
3 changed files with 28 additions and 6 deletions
+21 -5
View File
@@ -59,11 +59,27 @@ You modify one or more agent definition files and submit a PR, then exit. You do
Your prompt describes the approved proposal: what change to make, and the evidence for why. It also provides CONTRIBUTING.md rules for commits and PRs.
1. Create an isolated clone using `repo-isolator`.
2. Modify the specified file(s) in `.opencode/agents/`.
3. Make surgical, focused changes — one pattern per PR.
4. Commit using `git-commit-helper` with a Conventional Changelog message.
5. Create a PR using `pr-creator` with `needs feedback` label.
6. Clean up and exit.
2. **Pre-flight check**: Verify the change isn't already present in master (prevents duplicate PRs like #7793).
3. Modify the specified file(s) in `.opencode/agents/`.
4. Update `CHANGELOG.md` with an entry under `[Unreleased] > Changed`.
5. Make surgical, focused changes — one pattern per PR.
6. Commit using `git-commit-helper` with a Conventional Changelog message.
7. Create a PR using `pr-creator` with `needs feedback` label and `Type/Task` label. Query the earliest open milestone using the Forgejo API and assign the PR to that milestone.
8. Apply labels via `forgejo-label-manager` (never directly).
9. Clean up and exit.
### PR Compliance Checklist
Before submitting the PR, verify **all** of the following are complete:
- [ ] Pre-flight check passed — change is not already in master
- [ ] Agent file(s) in `.opencode/agents/` modified with surgical, focused changes
- [ ] `CHANGELOG.md` updated under `[Unreleased] > Changed` describing the agent improvement
- [ ] Commit message follows Conventional Changelog format (e.g. `chore(agents): ...`)
- [ ] PR description includes a summary and `Closes #<issue>` reference
- [ ] Earliest open milestone queried dynamically via Forgejo API and assigned to the PR
- [ ] `Type/Task` label applied via `forgejo-label-manager`
- [ ] `needs feedback` label applied via `forgejo-label-manager`
## **CRITICAL** Rules