@xevy/skills 0.1.28 → 0.1.29

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. Work runs locally by default; pass --cloud to use the server Web Agent. The coding agent reviews and corrects the result after every action.",
5
- "version": "0.1.28",
5
+ "version": "0.1.29",
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.28",
3
+ "version": "0.1.29",
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": [
@@ -12,9 +12,11 @@ Local analysis is the default. Pass the exact standalone `--cloud` flag to deleg
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve the task
20
22
 
@@ -12,9 +12,11 @@ Local implementation is the default. Pass the exact standalone `--cloud` flag to
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve and apply common gates
20
22
 
@@ -12,9 +12,11 @@ Local rework is the default. Pass the exact standalone `--cloud` flag to delegat
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -12,9 +12,11 @@ Local-only merge is the default. Pass the exact standalone `--cloud` flag to hav
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -32,7 +34,11 @@ Run verification for the merged scope: inspect `git status`, then run the projec
32
34
 
33
35
  ### Local safety rules
34
36
 
35
- - The merge is local only. Do not push and do not change task status; in particular, do not move the task to `done`. The user pushes manually from the main worktree.
37
+ - The merge stays in this working copy. Do not `git push` anything — not the base branch, not the feature branch, not tags.
38
+ - Do not open, update, or merge a pull request, and do not call the GitHub merge API, `gh pr merge`, or `gh pr create`. Landing the branch on the remote is the Cloud workflow's job and requires `--cloud`.
39
+ - Do not change task status; in particular, do not move the task to `done`.
40
+ - Do not deploy main, and do not "land it through a PR first" to make the merge visible remotely. If the user wants main updated, say the merge is local and unpushed, and let them decide what to do next.
41
+ - The user pushes manually from the main worktree.
36
42
  - Keep the task worktree for iteration; do not delete it.
37
43
 
38
44
  ## 2B. Cloud workflow (`--cloud`)
@@ -51,6 +57,8 @@ The server agent verifies the open-subtasks gate, syncs the base into the featur
51
57
  - If conflicts remain or tests fail, fix them on the feature branch; never push a protected branch directly. Re-verify before finishing.
52
58
  - Report PASS/PARTIAL/FAIL with evidence. Merge mode must not move the task to `done`.
53
59
 
54
- ## 3. Main deploy (optional, policy-aware)
60
+ ## 3. Main deploy — cloud workflow only (optional, policy-aware)
55
61
 
56
- If the user wants main updated, `mcp__xevy__deploy_main` deploys the project's remote default branch. Never push protected branches (`master`, `main`, `develop`, `staging`) to make main reflect local work; land changes through a PR first and warn that main shows the remote/PR-merged state. In the local workflow, an unpushed merge will not appear in main. Report the main URL.
62
+ This step does not apply to the Local workflow. After a local merge, report that the merge is local and unpushed, so main cannot reflect it, and stop there.
63
+
64
+ In the Cloud workflow, if the user wants main updated, `mcp__xevy__deploy_main` deploys the project's remote default branch. Never push protected branches (`master`, `main`, `develop`, `staging`) to make main reflect local work, and warn that main shows the remote/PR-merged state. Report the main URL.
@@ -12,9 +12,11 @@ Local QA handoff is the default. Pass the exact standalone `--cloud` flag to del
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve
20
22
 
@@ -12,9 +12,11 @@ Local planning is the default. Pass the exact standalone `--cloud` flag to deleg
12
12
 
13
13
  ## 0. Choose the engine
14
14
 
15
- - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy` as the flag.
16
- - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`.
17
- - With `--cloud`, follow the **Cloud workflow**.
15
+ - Parse `$ARGUMENTS` for the exact standalone `--cloud` token and remove that token before resolving the task. Do not treat similar text such as `--cloudy`, `cloud`, or `--cloud=true` as the flag.
16
+ - Without `--cloud`, follow the **Local workflow** and do not call `start_ai_action`. The missing flag is an explicit instruction to stay local: for the whole run, `mcp__xevy__start_ai_action`, `mcp__xevy__get_ai_execution`, and `mcp__xevy__list_ai_executions` are forbidden, and so is any other way of handing the work to the Xevy server agent.
17
+ - Never infer the cloud engine from context. Task status, an earlier cloud run, an open pull request, an existing execution record, an idle local worktree, urgency, or a local step that turns out to be slow or hard are **not** consent. Only the literal flag selects the Cloud workflow.
18
+ - If the Local workflow cannot be completed, stop and report exactly what is blocking it, then let the user decide whether to rerun with `--cloud`. Never switch engines mid-run and never run both.
19
+ - With `--cloud`, follow the **Cloud workflow** and do not duplicate the work locally beyond the review-and-correct step it defines.
18
20
 
19
21
  ## 1. Resolve the task
20
22