@xevy/skills 0.1.62 → 0.1.63

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.62",
5
+ "version": "0.1.63",
6
6
  "author": {
7
7
  "name": "Xevy"
8
8
  },
package/README.md CHANGED
@@ -138,7 +138,7 @@ Use generate-guide to make docs/guides/customer-form/manual.md with screenshots
138
138
 
139
139
  Computer works across desktop and browser apps and projects. Windows uses the signed-in desktop; macOS 14+ requires native Screen Recording and Accessibility consent. The guide workflow stays in the active engine, respects blocks and human take-over, and identifies incomplete verification or publication. Execute/fix use it for UI journeys when an authorized test environment is available.
140
140
 
141
- The package version is `0.1.62`. Run `npx @xevy/skills update -y` after that version is published.
141
+ After a new package version is published, run `npx @xevy/skills update -y` to update your installation.
142
142
 
143
143
  ## Security
144
144
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@xevy/skills",
3
- "version": "0.1.62",
3
+ "version": "0.1.63",
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": [
@@ -20,7 +20,9 @@ Local implementation is the default. Pass the exact standalone `--cloud` flag to
20
20
 
21
21
  ## 1. Resolve and apply common gates
22
22
 
23
- - Resolve the task and read its current numbered Plan and linked visualization. Read the current Plan with `get_task_plan`. Show a short plan before substantial changes and wait for the user’s go-ahead. Continue approved work without asking again. Preserve original requirements and legacy history. An Analysis section and generated subtasks are never prerequisites.
23
+ - Resolve the task and read its current numbered Plan and linked visualization. Read the current Plan with `get_task_plan` and the saved `storyPoints` with `find_task`. Before implementation or dispatching the cloud Execute action, ensure planning is complete and the Xevy task has `storyPoints > 0`, including when no active sprint exists.
24
+ - If the Plan is missing or no longer covers the requested scope, follow [plan](../plan/SKILL.md) first in the selected engine, including investigation, the canonical numbered Plan, linked visualization, and a saved story-point estimate. If only the estimate is missing or zero, size the existing Plan using `1, 2, 3, 5, 8, 13`, save `storyPoints` with `update_task`, and record a brief rationale. Re-read the task and Plan to confirm both prerequisites. If planning or saving the estimate is blocked, stop before implementation and report the gap.
25
+ - Show a short plan before substantial changes and wait for the user’s go-ahead. Continue approved work without asking again. Preserve original requirements and legacy history. An Analysis section and generated subtasks are never prerequisites.
24
26
  - Sprint gate: if an active sprint exists and the task is not on it, require the Plan and `storyPoints` greater than zero, then call `assign_task_to_sprint`. Record missing sprint prerequisites as blocked and preserve authorization gates.
25
27
 
26
28
  ### Code-only checklist and resume fallback
@@ -35,7 +35,9 @@ Example stored in Xevy:
35
35
  1. Remove Analyze — Remove the action from task controls, runner schemas, prompts, and packaged skills; retain historical executions and decisions.
36
36
  2. Simplify Plan — Write numbered technical steps to the task description; remove automatic subtask generation.
37
37
 
38
- Plan creates zero subtasks. Preserve existing subtasks and treat them as legacy guidance. Do not convert numbered steps into subtasks, a trace-matrix document, or a required checklist. Keep verification details in separate **QA Notes** or **Technical Review Instructions** when needed. Estimate `storyPoints` during Plan when the project uses sprint estimates.
38
+ Plan creates zero subtasks. Preserve existing subtasks and treat them as legacy guidance. Do not convert numbered steps into subtasks, a trace-matrix document, or a required checklist. Keep verification details in separate **QA Notes** or **Technical Review Instructions** when needed.
39
+
40
+ Estimate the planned scope using the story-point scale `1, 2, 3, 5, 8, 13` and persist the estimate in the Xevy task's `storyPoints` field with `update_task`. Include a brief sizing rationale in the Plan. This applies to every task, including tasks outside a sprint. Re-read the task with `find_task` and confirm `storyPoints > 0` before presenting Plan as complete; a number written only in prose does not complete estimation.
39
41
 
40
42
  ### Link the visualization
41
43
 
@@ -58,4 +60,4 @@ Explain unresolved decisions or missing visualization separately and keep affect
58
60
 
59
61
  Call `start_ai_action({ taskId, action: "plan", stream: true })` and report live progress. If a genuine disconnect ends the stream early, resume through `get_ai_execution` or `list_ai_executions`. On failure, report the captured output and offer a retry in the selected engine.
60
62
 
61
- Read the canonical task description Plan and any existing plan spec. Inspect referenced code and validate the numbered steps, concise technical details, requirement coverage, real linked task Artifact, and zero generated subtasks. Correct gaps in the task Plan, any existing matching spec, or Artifact; leave legacy subtasks intact. Apply the same short-title chat presentation and guidance as local planning. The server owns status automation.
63
+ Read the canonical task description Plan and any existing plan spec. Inspect referenced code and validate the numbered steps, concise technical details, requirement coverage, real linked task Artifact, and zero generated subtasks. Apply the same estimation and read-back requirements as local planning: confirm the task has saved `storyPoints > 0` and correct missing estimates with `update_task`. Correct gaps in the task Plan, any existing matching spec, or Artifact; leave legacy subtasks intact. Apply the same short-title chat presentation and guidance as local planning. The server owns status automation.
@@ -22,7 +22,7 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
22
22
  ## 2. Establish task intent (when linked)
23
23
 
24
24
  - Look for an explicit Xevy task code/link in the PR title, body, branch, or project metadata. Do not assume a coincidental code is a link; ask if ambiguous.
25
- - Resolve the linked task by code and read its original requirements plus relevant Analysis, specs, subtasks, decisions, and QA/review notes as needed. Check open decisions before task-based review; surface unresolved decisions rather than inventing expected behavior.
25
+ - Resolve every linked Xevy task by code and read its original requirements plus relevant Analysis, specs, subtasks, decisions, and QA/review notes as needed. Check open decisions before task-based review; surface unresolved decisions rather than inventing expected behavior. Record each distinct linked task and its freshly fetched current status for the final response; never infer status from a PR, prior lookup, or another task.
26
26
  - Inspect the full commit history contributing to the PR, not only the final diff or latest commit. Review commit messages, per-commit diffs, and relevant earlier versions to understand intent, identify inherited/unrelated work, and distinguish deliberate changes from regressions or accidental omissions. Compare the PR head to its current base for the final behavior; history provides intent/context and does not excuse a defect in the final state.
27
27
  - Check for multiple tasks in the PR title/body, branch, every commit message, and changed scope, including inherited commits. Deduplicate aliases that reference the same task (for example a Xevy code and its external tracker code); multiple identifiers alone do not prove multiple tasks. Distinguish intentionally included work from historical references or dependencies. Resolve identifiable additional Xevy tasks with targeted reads and check their status, remaining requirements, and relevance to the intended task. Do not assume a task is complete from its status alone or incomplete solely because it is not done.
28
28
  - If no task is linked, review against the PR's stated objective and repository conventions. State that task-requirement coverage could not be assessed.
@@ -47,7 +47,7 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
47
47
  - Use plain-text headings and numbered or bulleted lists only; **never use Markdown tables**. Keep the developer-facing response short, actionable, and easy to copy and paste. Do the full review and maintain internal ledgers, but do not print exhaustive inventories or checklists unless requested. Avoid repeating evidence across sections.
48
48
  - At response time, obtain the actual current datetime from the system clock and convert it to **GMT+8** (UTC+08:00), for example with `TZ=Etc/GMT-8 date --iso-8601=seconds`; do not guess it. Immediately after the opening merge indicator, include **Reviewed at:** with an ISO 8601 datetime ending in `+08:00`. If the clock cannot be read, explicitly state that the timestamp is unavailable.
49
49
  - Start with exactly one explicit merge indicator, then the linked task code immediately before the PR URL, followed by a brief reason and the reviewed head/base SHAs. Format: `**<MERGE INDICATOR>** — <TASK-CODE> — <PR-URL>`. If multiple distinct tasks are linked, list their codes comma-separated before the PR URL. If no task is resolved, use `NO LINKED TASK` before the PR URL:
50
- - **NOT SAFE TO MERGE** — a confirmed release blocker, conflict, failed required check, draft status, or unmet review/branch-protection gate remains. Distinguish code-safety blockers from procedural merge gates in the reason. This takes precedence over unverified checks; still report verification gaps.
50
+ - **NOT SAFE TO MERGE** — a confirmed release blocker, conflict, failed required check, draft status, unmet review/branch-protection gate, or linked task below QA remains. For every linked task, show its identifier and freshly checked current status in the response. Only `for_qa`, `verified`, and `done` satisfy this task-status gate; `draft`, `ready`, `planned`, `in_progress`, and `qa_failed` are procedural **NOT SAFE TO MERGE** blockers even when code and checks pass. Unknown, inaccessible, or stale status is unverified and cannot satisfy the gate; refresh all linked task statuses immediately before the verdict. Continue the complete PR review and report code findings regardless of task status. Never change task records or statuses. Distinguish code-safety blockers from procedural merge gates in the reason. This takes precedence over unverified checks; still report verification gaps.
51
51
  - **SAFE TO MERGE WITH NON-BLOCKING ISSUES** — full changed scope reviewed, no confirmed blockers or unresolved material safety questions, no conflicts, required checks passed and merge gates satisfied; only non-blocking findings remain.
52
52
  - **SAFE TO MERGE** — the same verification and gate conditions are satisfied, with no outstanding findings in the reviewed scope. This is a scoped recommendation, not a guarantee of defect-free code.
53
53
  - **MERGE SAFETY UNVERIFIED** — no confirmed blocker is established, but missing evidence, checks, incomplete scope, or stale SHAs prevent a supported safe verdict.
@@ -57,6 +57,6 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
57
57
  - Include a short **Warnings / Questions** section when needed for intentional changes that may surprise reviewers, ambiguous intent, suspected risks, multiple-task scope, or material unverified behavior. Explain what is observed, why it may matter, and what intent/evidence needs confirmation. Do not list intended behavior as a finding; when intent is confirmed, describe it only as an informational warning if it is useful to alert reviewers. Keep warnings separate from confirmed defects and blockers. Reflect unresolved material safety questions in the merge indicator. Omit the section when there is nothing material to flag.
58
58
  - On repeat reviews, provide a finding ledger: each prior finding marked fixed/still present/unverified, plus each new finding's evidenced origin (fix change, base change, pre-existing miss, or unknown). Explicitly acknowledge a pre-existing miss rather than calling it a regression. Compare coverage gaps with the earlier report.
59
59
  - Summarize verification in 1–3 bullets: what passed, material unverified flows, and access limitations. Keep the complete risk-based test matrix and every affected file/flow in the internal coverage ledger; include detail in the response only for consequential gaps or on request. If the full changed scope cannot be reviewed, use **MERGE SAFETY UNVERIFIED** unless a confirmed blocker already requires **NOT SAFE TO MERGE**.
60
- - When a task is linked, list requirements as concise bullets labeled met, partial, unmet, or unverified, each with evidence. Without a task, explicitly note that task coverage was not assessed.
60
+ - When tasks are linked, list every linked task identifier with its freshly refreshed status and gate result, then list requirements as concise bullets labeled met, partial, unmet, or unverified, each with evidence. Unknown/inaccessible task statuses must be explicitly marked unverified and are procedural blockers. When multiple tasks are linked, every task must pass the status gate; one failing task blocks the recommendation. Without a task, explicitly note that task coverage was not assessed.
61
61
  - State limitations (missing credentials, unavailable checks, unrun tests, stale mergeability, uncertain task link). Say “no issues found in the reviewed scope,” not “no issues exist,” when appropriate.
62
62
  - Do not merge or modify records as a consequence of a favorable verdict. Offer a separate follow-up if fixes or a merge are wanted.