@xevy/skills 0.1.67 → 0.1.68

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.
@@ -2,7 +2,7 @@
2
2
  "name": "xevy",
3
3
  "displayName": "Xevy",
4
4
  "description": "Native Xevy SDLC and Features workflows through MCP: plan, implement, review, record QA evidence and publish verified screenshot guides.",
5
- "version": "0.1.67",
5
+ "version": "0.1.68",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.67",
3
+ "version": "0.1.68",
4
4
  "description": "Install Xevy agent skills and secure per-agent MCP transports for Cursor, Claude Code, Codex, and other coding agents.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -68,6 +68,7 @@ Review the exact PR and report evidence-based findings. Review remains **read-on
68
68
 
69
69
  ## 5. Post the completed verdict as one PR comment
70
70
 
71
+ - **Always deliver the complete verdict in the user-facing conversation** on every completed review — when the comment posts successfully, when the user opts out, and when posting fails or is uncertain. The PR comment duplicates the verdict for GitHub readers; it never replaces the chat response. A comment-only reply without the verdict in conversation is a defect.
71
72
  - Post **exactly one comment per completed review**, only after the complete verdict is established, unless the user explicitly says not to post. Never post mid-review or for aborted/inaccessible PRs. A completed review may report blockers or unverified checks; do not turn a posting failure into a favorable verdict.
72
73
  - Render the full verdict from step 4 as one Markdown comment (headings and bullets, no tables), not just a teaser or link. Include the merge indicator and reviewed head/base SHAs, PR URL, every linked task code and freshly refreshed status (or Not linked/Unverified), the actual **Reviewed at:** timestamp, all findings and their **If not fixed:** and **Error if not fixed: Yes / No / Unverified** details, warnings, verification summary and limitations, and concise requirement coverage. End with the exact attribution footer: `🤖 Review generated by Xevy's review-pull-request skill`.
73
74
  - On local checkouts with an existing authenticated `gh` login, verify the PR/repository identity and run `gh pr comment <PR> --body-file <tempfile>` in the PR's checkout. Use a private temporary UTF-8 file, not shell interpolation of verdict text; remove that temporary file afterwards. Do not expose credentials or request a new local login as a fallback from a Dev Session.