ryan
d4800be3b7
Chore App Build, Test, and Push Docker Images / build-and-push (push) Successful in 3m17s
28 lines
1.2 KiB
Markdown
28 lines
1.2 KiB
Markdown
---
|
|
name: bugfix
|
|
description: "Executes a bugfix pipeline on one or more gitea issues: Developer -> Tester -> Reviewer"
|
|
---
|
|
|
|
## What I do
|
|
|
|
I orchestrate a sequential bugfix and verification pipeline - I will retrieve issues(s) from Gitea (title, body, images, comments, etc...). I will then forward information from the issues to the respective subagents.
|
|
|
|
Use gitea-mcp-server to interact with Gitea. Verify that the server is running and accessible.
|
|
|
|
If an issue is not provided, ask the user for the issue number(s).
|
|
|
|
1. **Developer**: Provides a code fix for each issue.
|
|
2. **Reviewer**: Audits the code and architectural soundness.
|
|
3. **Tester**: Runs tests related to the bugfix and determines if new unit tests, integration tests, or end-to-end tests are needed. If so, implement. Verify by running the test suite.
|
|
|
|
## Execution Rules
|
|
|
|
- Stop and ask the user for clarification if a step fails or is ambiguous.
|
|
- Use the `@` mention to trigger the respective subagents sequentially.
|
|
- Pass the context from the previous stage to the next stage to ensure consistency.
|
|
- Use multiple subagents to handle different aspects of the bugfix process if it will help.
|
|
|
|
## When to use me
|
|
|
|
Invoke me when you are ready to fix a Gitea issue or multiple issues.
|