@xevy/skills 0.1.53 → 0.1.54

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.53",
5
+ "version": "0.1.54",
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.53",
3
+ "version": "0.1.54",
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": [
@@ -19,9 +19,13 @@ For parallel work, start a separate agent session for each agent and keep its se
19
19
 
20
20
  ## Browser control
21
21
 
22
- For browser work, use tab-scoped browser actions when the companion advertises them. Reuse the current authenticated Agent session’s Computer session, then call `browser.discover` through `computer_action` and read its `computer_command` result. Select the browser and profile named by the user; otherwise use the relevant open browser/profile shown by discovery. Do not infer a profile from a window title alone.
22
+ For browser work, use tab-scoped browser actions when the companion advertises them. Reuse the current authenticated Agent session’s Computer session, then call `browser.discover {}` through `computer_action` and read its terminal `computer_command` result. Discovery lists browser IDs, profile IDs, and endpoint status; inspect it at the start of browser work. Select the browser and profile named by the user; otherwise use the relevant open browser/profile shown by discovery. Prefer a `ready` endpoint for the selected profile. Do not infer a profile from a window title alone.
23
23
 
24
- Call `browser.connect` with the selected `browserId` and `profileId` to attach to an existing local debugging endpoint. A running browser with a usable endpoint should remain open. If there is no endpoint, explain that starting debugging requires closing and reopening the selected browser/profile. Send `restart: true` only when that restart is authorized; never terminate another profile to obtain a port. The companion owns the loopback debugging connection. Do not connect directly to a debug port from the agent host or expose it across the network.
24
+ Call `browser.connect {browserId,profileId}` using IDs from discovery. It attaches to an existing local debugging endpoint without closing the browser, and launches a stopped profile with local debugging when no endpoint exists. If the selected profile is running without debugging, the first connect reports `browser_busy`. Use `browser.connect {browserId,profileId,restart:true}` to close and reopen that profile through the companion. A request to use the Computer includes routine browser recovery within its scope; the Browser category alone supports this action, so Shell access and manual close/open steps are unnecessary. Preserve known unsaved work. Leave other agents' sessions and profiles untouched; the companion rejects a restart when they share the selected process or endpoint. The companion owns the loopback debugging connection. Do not connect directly to a debug port from the agent host or expose it across the network.
25
+
26
+ Troubleshoot from the terminal result before asking for help. On `browser_selection_stale`, run discovery again and use the new IDs. On `browser_disconnected`, `browser_connection_lost`, or an unavailable endpoint, inspect current discovery and reconnect the selected profile. On `browser_tab_missing`, refresh `browser.tabs` and use the current tab ID or open a task-owned tab. On `browser_shared_session` after a restart attempt, attach to a ready endpoint without restart and use a separate task-owned tab, or choose an independent browser. On `browser_shared_process`, leave the shared process running and choose an independent browser or approved Desktop route. `chrome_default_profile` means Chrome requires a separate data directory for remote debugging. Choose another controllable browser or approved Desktop route; report the exact missing prerequisite if the requested profile cannot be controlled. If a full-page capture exceeds the limit or the page changes during capture, use a viewport snapshot or `browser.inspect`. If typing reports `browser_not_editable`, inspect the page, focus the intended field, and retry once its state is clear. Poll each command until terminal status; avoid repeating a write when its outcome is uncertain.
27
+
28
+ When Browser control remains unavailable, inspect `computer_get`, `computer_session`, device state, permissions and the returned error. If Desktop is approved, observe `desktop.windows`, `desktop.monitors` and `desktop.snapshot`, then use supported Desktop actions to continue the task and release the focus lease afterward. A device that is offline or locally paused, an unapproved capability, or a block rule requires its specific prerequisite; report that reason and the work still possible under current control. Do not request Shell solely to repair browser debugging, change owner permissions, disable rules, or take over another agent's session.
25
29
 
26
30
  Create a task-owned tab with `browser.newTab {url}` before parallel browser work, then use `browser.tabs`, `browser.navigate`, `browser.snapshot`, `browser.inspect`, `browser.click`, `browser.scroll`, `browser.type`, and `browser.key` as needed. `browser.snapshot {tabId,fullPage:true}` captures a bounded full page; `browser.inspect {tabId,selector?,limit?}` returns page title, URL, and bounded element metadata without running an arbitrary script. `browser.closeTab {tabId}` closes a tab owned by your session. A second agent cannot change a tab another agent owns; use a separate tab. Read every terminal command result and request a fresh snapshot after input. Use its saved reference and server evaluation to verify the changed page. Successful input dispatch establishes execution; verify the application outcome separately. Browser coordinates belong to the selected tab viewport; they are distinct from desktop screen coordinates. Prefer `browser.snapshot` for evidence because it captures the tab without unrelated desktop windows. `browser.disconnect` releases this session's browser connection; it closes a managed browser only when no other session uses it. Follow the tool's current schema and capability list, since older companion versions may offer desktop actions only.
27
31
 
@@ -81,7 +85,7 @@ Keep a stable `operationId` for one outcome across clicks, waits, retries, and s
81
85
 
82
86
  ## Blocks, data, and evidence
83
87
 
84
- Enabled action/application block rules govern every action. Report the matching rule and reason. Change a rule only under an explicit user instruction through an available owner tool; automatic rule disabling or bypassing a block is forbidden. Local keyboard/mouse interference pauses automation. These controls provide exclusive ownership and blocks; this workflow adds no per-action permission engine or prompts.
88
+ Enabled action/application block rules govern every action. Report the matching rule and reason. Change a rule only under an explicit user instruction through an available owner tool; automatic rule disabling or bypassing a block is forbidden. Local keyboard and mouse input keeps approved agent sessions active. The owner can explicitly Pause or End a session, or turn a capability Off, to stop the corresponding work. These controls provide exclusive ownership and blocks; this workflow adds no per-action permission engine or prompts.
85
89
 
86
90
  Use an authorized account and safe test fixtures. Keep credentials in the existing authenticated session or approved credential mechanism. User authorization governs external writes: a walkthrough or test uses the agreed test environment and records. Unexpected production changes, customer messages, financial transactions, or destructive writes require their own authorization.
87
91
 
@@ -1,6 +1,6 @@
1
1
  ---
2
2
  name: create-xevy-task
3
- description: Capture the current coding-agent session's AI work into a reviewable Xevy task — document the user's goal + requirements and everything the AI changed (files, branch, PR, preview), create the task, attach PR/branch metadata, and move it to for_review or for_qa so a human developer or QA can pick it up. Also creates an ordinary new task when there is nothing to capture.
3
+ description: Capture the current coding-agent session's AI work into a reviewable Xevy task — document the user's goal + requirements and everything the AI changed (files, branch, PR, preview), create the task, attach PR/branch metadata, and move it to for_qa so the existing QA owners can pick it up. Also creates an ordinary new task when there is nothing to capture.
4
4
  argument-hint: "[title or description] [--review|--qa]"
5
5
  disable-model-invocation: true
6
6
  allowed-tools: "Read Grep Bash mcp__xevy__find_task mcp__xevy__list_tasks mcp__xevy__get_project_workbreakdown mcp__xevy__create_task mcp__xevy__update_task mcp__xevy__update_task_status mcp__xevy__create_task_note mcp__xevy__get_deploy_status mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision"
@@ -53,10 +53,10 @@ After the task exists, if scope, approach, category/epic placement, or trade-off
53
53
 
54
54
  ## 5. Attach reviewer/QA guidance + set status
55
55
  - **404 recovery:** If a note call returns `Task not found`, do NOT retry it — the task doesn't exist yet; call `create_task` first and use its returned `task.id`.
56
- - **Who picks it up next?** If `$ARGUMENTS` has `--review` or `--qa`, use that; otherwise ask: a **developer** (code review → `for_review`) or **QA** (testing → `for_qa`)?
56
+ - **Who picks it up next?** Hand off to existing QA owners in `for_qa`. Legacy `--review` and `--qa` flags both use this handoff, not a replacement developer approval gate.
57
57
  - **For developer review:** add a `Technical Review Instructions` note (`create_task_note`) — what changed and where, how to run it locally, and the risk areas to scrutinise.
58
58
  - **For QA:** add a `QA Re-Testing Guide` note — non-technical and UI-verifiable: (1) preconditions, (2) step-by-step reproduction with expected vs actual, (3) validation checks, (4) evidence to capture, (5) final verdict.
59
- - Set the status with `update_task_status` to `for_review` or `for_qa`. NEVER jump to `done` — a human owns that gate.
59
+ - Set the status with `update_task_status` to `for_qa`. NEVER jump to `verified` or `done` — human QA Passed sets Verified and a separate manual Mark Done action completes the task.
60
60
 
61
61
  ## 6. Ordinary mode
62
62
  No AI work to capture (or a fresh, unrelated task): create the task from `$ARGUMENTS`/the request. Capture the user's story, problem, expectation, and desired outcome in plain language — do NOT fabricate technical detail or a PR. Raise any genuine ambiguities with `create_decision` (section 4b). Leave status at `draft` — use `/xevy:mark-ready` to promote once open questions are answered. Do NOT set `ready` while any decision is still open. Skip the review/QA routing.
@@ -45,7 +45,7 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered P
45
45
 
46
46
  ### Implement
47
47
 
48
- - Move the task to `in_progress` with `update_task_status` when implementation begins. This mirrors cloud execution, which moves to `in_progress` at start and `for_review` on success.
48
+ - Move the task to `in_progress` with `update_task_status` when implementation begins. This mirrors cloud execution, which moves to `in_progress` at start and `for_qa` on success.
49
49
  - Work through the approved numbered steps in order, committing coherent code milestones without requiring per-subtask checks or sign-off. When useful and supported, dispatch builder/frontend subagents with the worktree as their working directory. Keep changes surgical, match existing style, and update existing legacy subtask status through MCP only when applicable; never generate subtasks from the Plan.
50
50
  - Before editing UI pages, components, app shell, forms, or styling, follow `/xevy:xevy-design` and the project's `./.xevy/design.md`.
51
51
  - Apply the Decisions gate policy to material choices discovered during implementation.
@@ -54,7 +54,7 @@ Call `mcp__xevy__list_task_decisions` before implementing. Existing unanswered P
54
54
  ### Publish implementation
55
55
 
56
56
  - Commit and push the task branch. Open or refresh the PR and always give the user its PR or compare link. Do not merge automatically.
57
- - Record the branch on the task in `aiPullRequest.branch`, then move the task to `for_review` with `update_task_status`.
57
+ - Record the branch on the task in `aiPullRequest.branch`, then move the task to `for_qa` with `update_task_status`. Existing QA owners receive the handoff; AI must never set `verified` or `done`.
58
58
  - Do not deploy Preview automatically. Preview is an explicit user action via `/xevy:deploy preview`.
59
59
 
60
60
  ### Separate verification, QA, and review
@@ -14,7 +14,7 @@ This is the **human submission gate** from `draft` → `ready`. Draft is prepara
14
14
  Resolve from `$ARGUMENTS` (`mcp__xevy__find_task` by code) or the in-context task. If ambiguous, ask which task — never guess.
15
15
 
16
16
  ## 2. Check the current status
17
- Read the resolved task's status. `mark-ready` only promotes a task that is in **`draft`**. If it is already `ready` or further along (`planned` / `in_progress` / `for_review` / `for_qa` / `done`), STOP and report the current status — do **NOT** move it backwards. Continue only when the status is `draft`.
17
+ Read the resolved task's status. `mark-ready` only promotes a task that is in **`draft`**. If it is already `ready` or further along (`planned` / `in_progress` / `for_qa` / `qa_failed` / `verified` / `done`), STOP and report the current status — do **NOT** move it backwards. Continue only when the status is `draft`.
18
18
 
19
19
  ## 3. Answer open questions (MANDATORY gate)
20
20
  - Call `mcp__xevy__list_task_decisions` for the task.