poe-code 3.0.141 → 3.0.142

package/dist/prompts/github-issue-opened.md

@@ -7,29 +7,17 @@ label: "GitHub: Issue Handler"
 #   {{issue.title}}  - issue title
 #   {{issue.body}}   - issue body
 ---
-Read this newly opened GitHub issue and leave exactly one visible GitHub response.
-
-Issue URL: {{url}}
-Issue title: {{issue.title}}
-{{#issue.body}}
-Issue body:
-{{issue.body}}
-{{/issue.body}}
-
-Before answering:
-
-- Inspect the checked-out repository when the question is about current behavior, configuration, commands, or file paths.
-- Do not guess. Verify the answer against the repo before you post it.
-- When relevant, name the exact config key, env var, command, or file path you verified.
+Read {{url}} and leave a visible GitHub response.
 
 - If the issue is a question or needs only guidance, post a concise comment that directly answers it.
 - If the issue needs code changes, implement them, open or update a PR, and comment with the result.
 - If you cannot complete the request, comment with the blocker and the next concrete step.
 
-Make the visible response clean and easy to scan:
-
-- Start with a direct yes/no/decision sentence.
+- Start with a direct answer or decision.
 - Keep it concise.
-- If the repo supports configuration, explain how to configure it instead of only stating the default.
-- Use at most one short list for concrete details when it improves clarity.
-- Leave exactly one issue comment unless you are posting a PR follow-up.
+- Use short Markdown sections only when they improve clarity.
+
+Before answering:
+
+- Inspect the checked-out repository
+- Verify every claim against the repo before you post it.

package/dist/prompts/update-documentation.md

@@ -1,4 +1,8 @@
 ---
 label: "Scheduled: Update Documentation"
 ---
-Review recent code changes and update the documentation to reflect them.
+Review all commits that landed during the last 24 hours and update the documentation to reflect the full day's changes.
+
+Use the branch `agent/update-documentation` for this automation.
+If there is already an open, unmerged PR for that branch, update that existing PR with the new documentation changes instead of opening a new PR.
+If the documentation is already correct, leave the repository unchanged and do not open or update a PR.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "poe-code",
-  "version": "3.0.141",
+  "version": "3.0.142",
   "description": "CLI tool to configure Poe API for developer workflows.",
   "type": "module",
   "main": "./dist/index.js",