@xevy/skills 0.1.57 → 0.1.59
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.
|
|
5
|
+
"version": "0.1.59",
|
|
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
|
@@ -12,6 +12,8 @@ For a guide that teaches an application or feature journey, use [generate-guide]
|
|
|
12
12
|
|
|
13
13
|
## 1. Choose the format
|
|
14
14
|
|
|
15
|
+
For explicit LaTeX / `.tex` or XeLaTeX-generated Unicode PDF requests, use [create-latex](../create-latex/SKILL.md): privately save source and verify `get_attachment_preview` readiness. Unspecified formats still default to HTML.
|
|
16
|
+
|
|
15
17
|
Default to HTML when the user does not specify a format. This includes prose-first guides, reports, diagrams, and tabular content, so unspecified Artifacts open as readable pages in Xevy.
|
|
16
18
|
|
|
17
19
|
Honour an explicit format request, whether it appears in ordinary language, a filename extension, or `--format`. For example, "Markdown guide", `handoff.md`, and `--format md` all select Markdown. Use the following table to build the chosen format:
|
|
@@ -0,0 +1,41 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: create-latex
|
|
3
|
+
description: Create a XeLaTeX PDF artifact in Xevy Drive when the user asks for LaTeX, TeX, typeset mathematics, or a Unicode PDF.
|
|
4
|
+
argument-hint: "[document to typeset]"
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
# Create a LaTeX PDF
|
|
8
|
+
|
|
9
|
+
Create one `.tex` source artifact and request its isolated PDF preview. The `.tex` remains the canonical saved source; the preview is a separate derivative. Preserve Unicode with XeLaTeX and `fontspec`.
|
|
10
|
+
|
|
11
|
+
## Source template
|
|
12
|
+
|
|
13
|
+
```tex
|
|
14
|
+
% !TEX program = xelatex
|
|
15
|
+
\documentclass[11pt]{article}
|
|
16
|
+
\usepackage{fontspec}
|
|
17
|
+
\setmainfont{Latin Modern Roman}
|
|
18
|
+
\usepackage[margin=1in]{geometry}
|
|
19
|
+
\usepackage{graphicx}
|
|
20
|
+
\begin{document}
|
|
21
|
+
\section*{Title}
|
|
22
|
+
Unicode text and mathematics: $\int_0^1 x^2\,dx=\frac13$.
|
|
23
|
+
\end{document}
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Use only ordinary document content and supported packages; compilation runs in a restricted no-network environment. Preserve Unicode using the `fontspec` template above. For a background or logo, upload/select each authorized PNG/JPEG in project Drive and pin its exact immutable reference in a comment (never guess or use a floating/current alias):
|
|
27
|
+
|
|
28
|
+
```tex
|
|
29
|
+
% xevy-asset: assets/background.png xevy-image:ATTACHMENT_UUID@VERSION
|
|
30
|
+
\includegraphics[width=\textwidth]{assets/background.png}
|
|
31
|
+
% xevy-asset: assets/logo.png xevy-image:LOGO_ATTACHMENT_UUID@VERSION
|
|
32
|
+
\includegraphics[width=2cm]{assets/logo.png}
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
Do not invent UUIDs/versions, use remote URLs, arbitrary local paths, custom fonts/packages, or additional `.tex` inputs. Save one source `.tex` only: no editor workflow, ZIP/multifile bundles, or package uploads. Asset references must be private and explicitly versioned.
|
|
36
|
+
|
|
37
|
+
## Save and verify
|
|
38
|
+
|
|
39
|
+
1. Save the unchanged source as `application/x-tex` with filename ending `.tex` through `create_attachment` (private; never set public for pinned private images).
|
|
40
|
+
2. Call `get_attachment_preview` with the returned attachment UUID and version. Report a PDF preview only when the tool returns `status: ready` and its protected `pdfUrl`.
|
|
41
|
+
3. If unavailable or compilation fails, report that the source was saved and preview is unavailable; do not invent a PDF or URL. Keep the source available for download and retry preview when appropriate.
|
|
@@ -25,8 +25,8 @@ Review the exact pull request, repair merge conflicts and PR-caused failures on
|
|
|
25
25
|
- Run the project-relevant type-check, lint, test, and build checks. Separate failures caused by the pull request from known baseline failures when evidence permits.
|
|
26
26
|
- Inspect required GitHub checks, requested reviews, branch protection, draft state, and merge queue requirements.
|
|
27
27
|
- Classify each remaining finding as:
|
|
28
|
-
- `BLOCKER`: merging can cause incorrect behavior, security exposure, data loss, an incompatible contract, a failed required check, or a branch-protection violation.
|
|
29
|
-
- `ISSUE`: a valid follow-up concern whose impact does not make this pull request unsafe to merge.
|
|
28
|
+
- `BLOCKER`: merging can cause incorrect behavior, security exposure, data loss, an incompatible contract, a failed required check, a broken build, or a branch-protection violation that GitHub enforces, such as a required review that prevents merging.
|
|
29
|
+
- `ISSUE`: a valid follow-up concern whose impact does not make this pull request unsafe to merge. A missing approval record, missing or extra test coverage, documentation, style, and naming are always issues, never blockers.
|
|
30
30
|
- Give every finding a concise title, evidence, affected path or check, impact, and recommended action.
|
|
31
31
|
|
|
32
32
|
## 3. Repair conflicts and PR-caused failures
|
|
@@ -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.
|