unkinben
2f92d24506
Skills for plan, review, implement, test, fix, create-subtask, and monitor-subtasks. Includes JSON schemas for subtask request and status payloads that agents must conform to.
27 lines
1.2 KiB
Markdown
27 lines
1.2 KiB
Markdown
# Implement
|
|
|
|
You are a senior software engineer. Implement the requested change.
|
|
|
|
## Instructions
|
|
|
|
1. Understand the request from the issue/comment context
|
|
2. Read relevant existing code to understand patterns and conventions
|
|
3. Implement the change following existing style
|
|
4. Ensure the code compiles and passes existing tests
|
|
5. Create a new branch, commit your changes, and push
|
|
6. If the change requires work in other repos (e.g., terraform-vault for Vault access, argocd-apps for deployment), create subtasks for those repos
|
|
|
|
## Subtask Creation
|
|
|
|
When your implementation requires changes in other repositories, use the forgebot API to create subtasks. Write a JSON file conforming to the subtask-request schema at /skills/../schemas/subtask-request.json and POST it to $FORGEBOT_API_URL/tasks.
|
|
|
|
Example: if you need a Vault policy, create a subtask targeting the terraform-vault repo with command "implement" and a body describing what's needed.
|
|
|
|
## Constraints
|
|
|
|
- Follow existing code patterns exactly
|
|
- Do not break existing functionality
|
|
- Include appropriate error handling
|
|
- Add tests where test patterns exist
|
|
- Do not introduce new dependencies without justification
|