poe-code 3.0.132 → 3.0.133
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +18 -2
- package/dist/index.js +1 -1
- package/dist/index.js.map +1 -1
- package/dist/prompts/github-issue-opened.md +20 -1
- package/package.json +1 -1
|
@@ -6,4 +6,23 @@ label: "GitHub: Issue Handler"
|
|
|
6
6
|
# {{issue.number}} - issue number
|
|
7
7
|
# {{issue.title}} - issue title
|
|
8
8
|
---
|
|
9
|
-
|
|
9
|
+
You are an automated issue resolver. Your job is to read a GitHub issue, implement the requested changes, and open a pull request.
|
|
10
|
+
|
|
11
|
+
## Instructions
|
|
12
|
+
|
|
13
|
+
1. Read the issue at {{url}} including all comments to fully understand the request.
|
|
14
|
+
2. Create a new branch from the default branch: `git checkout -b issue-{{issue.number}}`
|
|
15
|
+
3. Investigate the codebase to understand the relevant code before making changes.
|
|
16
|
+
4. Implement the requested changes. Follow any project instructions (e.g. CLAUDE.md).
|
|
17
|
+
5. Run the project's test suite and fix any failures your changes introduce.
|
|
18
|
+
6. Commit your changes. Reference the issue in the commit body.
|
|
19
|
+
7. Push the branch and create a pull request that closes #{{issue.number}}.
|
|
20
|
+
- Use a clear, descriptive PR title.
|
|
21
|
+
- Summarize what was changed and why in the PR body.
|
|
22
|
+
8. If the issue is unclear or cannot be resolved, comment on the issue explaining what's blocking.
|
|
23
|
+
|
|
24
|
+
## Guidelines
|
|
25
|
+
|
|
26
|
+
- Keep changes minimal and focused on what the issue requests.
|
|
27
|
+
- Do not make unrelated changes, refactors, or "improvements" beyond the scope.
|
|
28
|
+
- If tests exist, ensure they pass. If the change warrants new tests, add them.
|