poe-code 3.0.148 → 3.0.149

package/dist/prompts/fix-vulnerabilities.md

@@ -4,15 +4,16 @@ source: >-
   gh api repos/{owner}/{repo}/dependabot/alerts --jq '[.[] |
   select(.state=="open")]'
 agent: claude-code
-# Available variables (each sourced Dependabot alert):
-#   {{number}}                                          - alert number
-#   {{dependency.package.name}}                         - vulnerable package name
-#   {{dependency.package.ecosystem}}                    - ecosystem (e.g. npm)
-#   {{dependency.manifest_path}}                        - path to manifest (e.g. package.json)
-#   {{security_advisory.ghsa_id}}                       - advisory ID
-#   {{security_advisory.summary}}                       - short description
-#   {{security_advisory.severity}}                      - low | medium | high | critical
-#   {{security_advisory.description}}                   - full advisory description
-#   {{security_vulnerability.first_patched_version.identifier}} - first safe version
+# Source fields: number, dependency.package.{name,ecosystem}, dependency.manifest_path,
+#   security_advisory.{ghsa_id,summary,severity,description},
+#   security_vulnerability.first_patched_version.identifier (first safe version)
 ---
 Fix {{dependency.package.name}} ({{security_advisory.severity}}): {{security_advisory.summary}}
+
+{{skill_github_cli}}
+
+{{pull_request_guidelines}}
+
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/prompts/github-issue-comment-created.md

@@ -8,32 +8,23 @@ prefix:
   - "poe-code"
   - "poe-code-agent"
   - "@poe-code-agent"
-# Available variables:
-#   {{url}}            - full GitHub URL to the issue
-#   {{repo}}           - owner/repo (e.g. acme/my-app)
-#   {{issue.number}}   - issue number
-#   {{issue.title}}    - issue title
-#   {{comment.author}} - login of the comment author
-#   {{comment.body}}   - body text of the triggering comment
 ---
 Read {{url}} and leave a visible GitHub response to the comment from {{comment.author}}: {{comment.body}}
 
 {{#pr.number}}
 - This comment is on pull request #{{pr.number}}.
-- If the comment asks for code changes or follow-up implementation, implement them on the current PR branch, update the existing PR, and comment with the result.
-- Do not open a new PR from a pull request comment unless updating the existing PR is impossible.
+- If the comment asks for code changes, implement them on the current PR branch, update the existing PR, and comment with the result.
+- Do not open a new PR unless updating the existing PR is impossible.
 {{/pr.number}}
 {{^pr.number}}
-- If the comment asks for code changes or follow-up implementation, make the changes, open or update a PR, and comment with the result.
+- If the comment asks for code changes, open or update a PR and comment with the result.
 {{/pr.number}}
-- If the comment only needs guidance or clarification, reply directly and concisely.
-- If you cannot complete the request, comment with the blocker and the next concrete step.
+- If blocked, comment with the blocker and next step.
 
-- Start with a direct answer or decision.
-- Keep it concise.
-- Use short Markdown sections only when they improve clarity.
+{{skill_github_cli}}
 
-Before answering:
+{{pull_request_guidelines}}
 
-- Inspect the checked-out repository
-- Verify every claim against the repo before you post it.
+{{response_style}}
+
+{{verify_before_responding}}

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

@@ -1,23 +1,15 @@
 ---
 label: "GitHub: Issue Handler"
-# Available variables:
-#   {{url}}          - full GitHub URL to the issue
-#   {{repo}}         - owner/repo (e.g. acme/my-app)
-#   {{issue.number}} - issue number
-#   {{issue.title}}  - issue title
-#   {{issue.body}}   - issue body
 ---
 Read {{url}} and leave a visible GitHub response.
 
 - If the issue needs code changes, implement them, open or update a PR, and comment with the result.
-- If the issue is a question or needs only guidance, post a concise comment that directly answers it. Be practical, give examples.
-- If you cannot complete the request, comment with the blocker and the next concrete step.
+- If blocked, comment with the blocker and next step.
 
-- Start with a direct answer or decision.
-- Keep it concise.
-- Use short Markdown sections only when they improve clarity.
+{{skill_github_cli}}
 
-Before answering:
+{{pull_request_guidelines}}
 
-- Inspect the checked-out repository
-- Verify every claim against the repo before you post it.
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/prompts/github-pull-request-opened.md

@@ -1,10 +1,12 @@
 ---
 label: "GitHub: Pull Request Handler"
-# Available variables:
-#   {{url}}       - full GitHub URL to the pull request
-#   {{repo}}      - owner/repo (e.g. acme/my-app)
-#   {{pr.number}} - pull request number
-#   {{pr.title}}  - pull request title
-#   {{pr.author}} - login of the PR author
 ---
 Read {{url}} and review the pull request.
+
+{{skill_github_cli}}
+
+{{code_review_guidelines}}
+
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/prompts/github-pull-request-synchronized.md

@@ -1,8 +1,12 @@
 ---
 label: "GitHub: Pull Request Update Handler"
-# Available variables:
-#   {{url}}       - full GitHub URL to the pull request
-#   {{repo}}      - owner/repo (e.g. acme/my-app)
-#   {{pr.number}} - pull request number
 ---
 Read {{url}} and re-review the updated pull request.
+
+{{skill_github_cli}}
+
+{{code_review_guidelines}}
+
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/prompts/update-dependencies.md

@@ -2,3 +2,11 @@
 label: "Scheduled: Update Dependencies"
 ---
 Update all dependencies to their latest compatible versions and open a pull request.
+
+{{skill_github_cli}}
+
+{{pull_request_guidelines}}
+
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/prompts/update-documentation.md

@@ -1,8 +1,15 @@
 ---
 label: "Scheduled: Update Documentation"
 ---
-Review all commits that landed during the last 24 hours and update the documentation to reflect the full day's changes.
+Review all commits that landed during the last 24 hours and update the documentation to reflect the changes on branch `agent/update-documentation`.
 
-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.
+If there is already an open, unmerged PR for that branch, update that existing PR instead of opening a new one.
+If the documentation is already correct, do not open or update a PR.
+
+{{skill_github_cli}}
+
+{{pull_request_guidelines}}
+
+{{response_style}}
+
+{{verify_before_responding}}

package/dist/variables.yaml

@@ -0,0 +1,23 @@
+# Preview rendered prompt: poe-code github-workflows prompt-preview <name>
+
+response_style: |
+  - Start with a direct answer or decision.
+  - Keep it concise.
+  - Use short Markdown sections only when they improve clarity.
+
+verify_before_responding: |
+  Before responding:
+  - Inspect the checked-out repository.
+  - Verify every claim against the repo before you post it.
+
+skill_github_cli: |
+  Use the `gh` CLI for all GitHub operations (issues, PRs, reviews, checks).
+
+pull_request_guidelines: |
+  - One logical change per PR. Feel free to open multiple PRs.
+  - Follow the repo guidelines
+
+code_review_guidelines: |
+  - Review every changed file, not just the diff summary.
+  - Verify the change follows existing patterns in the codebase. New abstractions need justification.
+  - Don't rubber-stamp. Request changes when there are real issues.

package/package.json

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