poe-code 3.0.213 → 3.0.215

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

@@ -8,9 +8,9 @@ allow:
 ---
 Read {{url}} and leave a visible GitHub response.
 
-- First assess if the issue is actionable: it must have a title that conveys intent AND a body with enough detail to understand the request. Empty bodies, one-word titles that are not a real product name, and gibberish do not qualify.
-- If the issue is not actionable, post a short comment explaining what's missing (e.g. "Closing: the body is empty and the title alone doesn't describe a reproducible issue. Please reopen with steps to reproduce or a clear feature request.") and close the issue with `gh issue close`. Do not apply labels.
-- If the issue is actionable and needs code changes, implement them, open or update a PR, and comment with the result.
+- Treat every newly opened issue as something that deserves a response. Use the title, body, attachments, and comments when deciding what to do.
+- If the issue does not include enough detail to make a code change, leave a short comment to ask for the missing details. Do not close the issue.
+- If the issue needs code changes, implement them, open or update a PR, and comment with the result.
 - If blocked, comment with the blocker and next step.
 - When posting any multiline GitHub comment or PR body, write it with a quoted heredoc and pass it to `gh` with `--body-file` instead of an inline `--body` string.
 

package/package.json

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