@xevy/skills 0.1.22 → 0.1.23

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. Cloud (server Web Agent) by default; '-here' variants run locally in this Claude Code session. Claude reviews and corrects the result after every action.",
5
- "version": "0.1.22",
5
+ "version": "0.1.23",
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.22",
3
+ "version": "0.1.23",
4
4
  "description": "Install Xevy agent skills and MCP for Cursor, Claude Code, Codex, and other coding agents — one command via npx skills + add-mcp.",
5
5
  "type": "module",
6
6
  "keywords": [
@@ -0,0 +1,15 @@
1
+ ---
2
+ name: clean-worktree
3
+ description: Remove a completed task's local git worktree safely after verifying the Xevy task is done. Never deletes branches or uncommitted work.
4
+ argument-hint: "[task]"
5
+ disable-model-invocation: true
6
+ allowed-tools: "Read Bash mcp__xevy__find_task"
7
+ ---
8
+
9
+ # Clean a completed task worktree
10
+
11
+ 1. Resolve `$ARGUMENTS` or the session task with `find_task`. Require task status `done`; otherwise stop.
12
+ 2. Locate the matching worktree with `git worktree list --porcelain`.
13
+ 3. In that worktree, require a clean `git status --short`. If changes exist, stop and report them.
14
+ 4. Return to the main worktree and run `git worktree remove <exact-path>` without `--force`.
15
+ 5. Run `git worktree prune`, verify the path is gone, and report it. Do not delete local or remote branches.
@@ -3,7 +3,7 @@ name: execute-here
3
3
  description: Execute a task locally in the current coding-agent session — worktree, implement against the plan, run tests, commit, push, open a PR, deploy a preview, then review/correct. Cloud equivalent is the execute skill.
4
4
  argument-hint: "[task]"
5
5
  disable-model-invocation: true
6
- allowed-tools: "Read Grep Edit Write Bash Agent mcp__xevy__find_task mcp__xevy__update_task mcp__xevy__update_task_status mcp__xevy__list_specs mcp__xevy__list_subtasks mcp__xevy__update_subtask mcp__xevy__list_sprints mcp__xevy__assign_task_to_sprint mcp__xevy__deploy_preview mcp__xevy__get_deploy_status mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision"
6
+ allowed-tools: "Read Grep Edit Write Bash Agent mcp__xevy__find_task mcp__xevy__update_task mcp__xevy__update_task_status mcp__xevy__list_specs mcp__xevy__list_subtasks mcp__xevy__update_subtask mcp__xevy__list_sprints mcp__xevy__assign_task_to_sprint mcp__xevy__deploy_preview mcp__xevy__get_deploy_status mcp__xevy__list_task_decisions mcp__xevy__create_decision mcp__xevy__answer_decision set_session_task_lock"
7
7
  ---
8
8
 
9
9
  # /xevy:execute-here — implement locally (then review + deploy)
@@ -18,6 +18,7 @@ You are the engine: implement the task in this session, following the Xevy workt
18
18
  ## 2. Worktree protocol
19
19
  - Record the current branch + dir. Derive a canonical branch `xevy/<TASK-ID>-<slug>` (task id = task code, or first 8 chars of task UUID; reuse if one already exists for this task — never create a second branch per task).
20
20
  - Create/attach a git worktree in a sibling dir and `cd` into it; if resuming, first merge the latest source branch (e.g. `git merge origin/main`). Do ALL work in the worktree.
21
+ - In Pi, call `set_session_task_lock(taskCode, taskId, taskTitle, worktreePath, branch)` immediately after attaching the worktree, using its absolute `git rev-parse --show-toplevel` path. If that tool is unavailable, continue—the worktree rules still apply.
21
22
  - NEVER commit/push on a protected branch (master/main/develop/staging) — only on `xevy/*` task branches.
22
23
 
23
24
  ## 3. Implement
@@ -3,7 +3,7 @@ name: xevy-setup
3
3
  description: Bootstrap Xevy for this repository — verify the MCP connection, pick a workspace/project (create one if the workspace is empty), link this repo, write .xevy/project.json, set Dockerfile-first deploy defaults, and sync any missing .env keys. Run once per repo.
4
4
  argument-hint: "[workspace/project]"
5
5
  disable-model-invocation: true
6
- allowed-tools: "Read Write Edit Bash mcp__xevy__get_current_user mcp__xevy__list_workspaces mcp__xevy__list_projects mcp__xevy__create_project mcp__xevy__get_project_workbreakdown mcp__xevy__update_project_preview_settings"
6
+ allowed-tools: "Read Write Edit Bash mcp__xevy__get_current_user mcp__xevy__list_workspaces mcp__xevy__list_projects mcp__xevy__create_project mcp__xevy__get_project_workbreakdown mcp__xevy__create_category mcp__xevy__create_epic mcp__xevy__update_project_preview_settings"
7
7
  ---
8
8
 
9
9
  # /xevy:xevy-setup — connect this repo to Xevy
@@ -49,8 +49,8 @@ The Xevy MCP server authenticates via **OAuth** when configured (run `npx @xevy/
49
49
  - NEVER `cat`/read/print `.env` or any env values yourself. The helper adds only keys not already configured and never overwrites existing values. If there is no `.env`, skip this step.
50
50
  - Auth note: the env-sync and repo-link helpers call the REST API (not MCP) and read an API key from `~/.config/xevy/credentials` (or `XEVY_API_KEY`). MCP itself uses OAuth; these two local helpers need a REST key. If none is present, tell the user to create one at Xevy → Settings → API keys, then re-run just these steps.
51
51
 
52
- ## 6. Bootstrap structure (optional)
53
- - If the project has no categories yet (`get_project_workbreakdown`), offer to create starter categories/epics — but do not create tasks. (Or tell the user to run a dedicated bootstrap later.)
52
+ ## 6. Bootstrap structure
53
+ - Read `get_project_workbreakdown`. Only when the project has no categories, create 3–6 user/product-area categories (never technical-layer categories such as Frontend or API) and 1–3 starter epics per category for already-present capabilities. If categories exist, skip this step. Never create tasks.
54
54
 
55
55
  ## 7. Report
56
56
  Summarise: workspace/project, repo link, deploy build pack + ports, count of env keys added (names only), and the next Xevy skills they can run (`analyze`, `execute`, `deploy`; slash-command names may be available in some clients). Do not print secrets.