@xevy/skills 0.1.57 → 0.1.58

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 workflow commands driven through the Xevy MCP server. Analyze, plan, execute, fix, and move-to-qa run locally by default and accept --cloud for the server Web Agent. Merge stays local; merge-pull-request evaluates and lands the remote PR.",
5
- "version": "0.1.57",
5
+ "version": "0.1.58",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/README.md CHANGED
@@ -118,6 +118,7 @@ with `codex mcp add`.
118
118
  | `merge [task]` | Merge a task branch locally for review; leaves remotes and pull requests unchanged |
119
119
  | `merge-pull-request [URL\|number\|branch]` | Evaluate a PR, repair conflicts, handle blockers, and merge it remotely |
120
120
  | `move-to-qa [task] [--cloud]` | QA handoff (local by default) |
121
+ | `move-to-verified [task]` | Record explicit QA approval and move an eligible task from For QA to Verified |
121
122
  | `deploy` | Coolify preview/main |
122
123
  | `investigate` | Diagnose with ephemeral scripts (.env; no secrets) |
123
124
  | `create-xevy-task` | Capture session work into a task |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.57",
3
+ "version": "0.1.58",
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": [
@@ -0,0 +1,31 @@
1
+ ---
2
+ name: move-to-verified
3
+ description: Record explicit human QA approval and move an eligible Xevy task from For QA to Verified. Never marks a task Done.
4
+ argument-hint: "[task]"
5
+ disable-model-invocation: true
6
+ allowed-tools: "mcp__xevy__find_task mcp__xevy__update_task_status"
7
+ ---
8
+
9
+ # /xevy:move-to-verified — record QA approval
10
+
11
+ Move a task to **Verified** only after the user explicitly confirms that human QA passed. Verified is not Done; marking Done remains a separate manual action.
12
+
13
+ ## 1. Resolve the task
14
+
15
+ Resolve `$ARGUMENTS` with `mcp__xevy__find_task` using the current workspace and project identifiers plus the task code. With no argument, use the task explicitly identified in the current context only when its identity is unambiguous. If there is no task, it is not found, or identity is ambiguous, stop and report that no change was made; do not guess or make a status call.
16
+
17
+ ## 2. Check eligibility
18
+
19
+ The `find_task` result includes the resolved task's current status and URL; inspect that result. Continue only when status is exactly `for_qa`. For any other or missing status—including `verified` or `done`—stop, report the observed status and task URL when available, and do not change it. Do not move tasks backwards or attempt a different transition.
20
+
21
+ ## 3. Obtain explicit approval
22
+
23
+ Ask the user to confirm that human QA has passed for this task. Automated tests, implementation completion, a review result, or the task being in For QA are not themselves QA approval. If the user declines or approval is unclear, stop without changing task data.
24
+
25
+ ## 4. Apply the single transition
26
+
27
+ Immediately before mutation, call `mcp__xevy__find_task` again with the same workspace identifier, project identifier, and task code. Confirm it still resolves uniquely to the same task UUID and its current status is exactly `for_qa`; if not, stop and report without mutation. Then call `mcp__xevy__update_task_status({ workspaceIdentifier, projectIdentifier, taskId, status: "verified" })` exactly once. The status API does not provide an atomic compare-and-set precondition: the re-read narrows but cannot eliminate a concurrent-change race. If the tool rejects the transition or reports a stale/current status conflict, stop and report; do not retry with another status or broader update.
28
+
29
+ ## 5. Confirm and report
30
+
31
+ Re-read using `mcp__xevy__find_task` with the same workspace identifier, project identifier, and task code; confirm it is still the same task and status is `verified`. Report task code, observed status, and task URL. If the result is not Verified or cannot be confirmed, say so plainly and do not retry. Never set `done`, deploy, or make unrelated task changes.