@xevy/skills 0.1.66 → 0.1.68
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 and Features workflows through MCP: plan, implement, review, record QA evidence and publish verified screenshot guides.",
|
|
5
|
-
"version": "0.1.
|
|
5
|
+
"version": "0.1.68",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Xevy"
|
|
8
8
|
},
|
package/README.md
CHANGED
|
@@ -118,7 +118,7 @@ with `codex mcp add`.
|
|
|
118
118
|
| `fix [task] [--cloud]` | Rework after review (local by default) |
|
|
119
119
|
| `merge [task]` | Merge a task branch locally for review; leaves remotes and pull requests unchanged |
|
|
120
120
|
| `merge-pull-request [URL\|number\|branch]` | Evaluate a PR, repair conflicts, handle blockers, and merge it remotely |
|
|
121
|
-
| `review-pull-request [URL\|number\|branch]` |
|
|
121
|
+
| `review-pull-request [URL\|number\|branch]` | Evidence-based PR review; posts the full verdict as one new PR comment by default (opt-out), with code, records, and merge remaining read-only |
|
|
122
122
|
| `move-to-qa [task] [--cloud]` | QA handoff (local by default) |
|
|
123
123
|
| `move-to-verified [task]` | Record explicit QA approval and move an eligible task from For QA to Verified |
|
|
124
124
|
| `deploy` | Coolify preview/main |
|
package/package.json
CHANGED
|
@@ -143,11 +143,11 @@ For other project images, retain the immutable handle returned by upload/generat
|
|
|
143
143
|
|
|
144
144
|
For other project Artifacts, prefer file transfer so the file bytes stay outside model context and MCP JSON arguments:
|
|
145
145
|
|
|
146
|
-
1. When `create_attachment` exposes `filePath`, call it with a regular file inside the registered temporary workspace or the tool’s permitted project path, exact `mimeType`, matching `fileName`, `description`, optional resolved `taskId`, and `public: false` unless the user explicitly requested a public/shareable Artifact. This
|
|
147
|
-
2. Through MCP, call `prepare_attachment_upload` with the exact filename, MIME type, byte size, description, optional task UUID, and
|
|
146
|
+
1. When `create_attachment` exposes `filePath`, call it with a regular file inside the registered temporary workspace or the tool’s permitted project path, exact `mimeType`, matching `fileName`, `description`, optional resolved `taskId`, and `public: false` unless the user explicitly requested a public/shareable Artifact. This transfers accepted files through authenticated Xevy validation up to 100 MB; images are limited to 25 MB. On an interrupted transfer, retry the same file and metadata to resume the existing attachment.
|
|
147
|
+
2. Through MCP, call `prepare_attachment_upload` with the exact filename, MIME type, byte size, description, optional task UUID, visibility, and a stable `requestKey` reused on retries. Transfer the local file bytes through an authenticated host helper to the returned Xevy application `uploadUrl` using the exact `uploadMethod` and `requiredHeaders`, then call `complete_attachment_upload` with the returned `attachmentId`. Keep authentication inside the host helper. Uploads use the Xevy application endpoint; keep OVH credentials and signed storage URLs outside model context. Completion validates the uploaded byte count, expands authorized HTML image references, and checks the final signature, embedded size and Artifact security state before the viewer URL becomes readable.
|
|
148
148
|
3. Use `create_attachment` with `textContent` for a small text-backed artifact or `sourceUrl` for an existing public binary when local transfer is unavailable. Export built-in image output to a local file with the host helper before uploading; keep binary/base64 bytes outside main-agent arguments.
|
|
149
149
|
|
|
150
|
-
Text-backed Artifacts remain limited to 10 MB after decoding for safe parsing and preview.
|
|
150
|
+
Text-backed Artifacts remain limited to 10 MB after decoding for safe parsing and preview. Authenticated file transfer supports PDFs and other accepted files up to 100 MB. Never split one Artifact across calls or place a large file in base64 tool arguments.
|
|
151
151
|
|
|
152
152
|
For a personal-note Artifact, call `create_note_attachment` with the content fields plus `noteId`. Note attachments are always private. Publishing a note is a separate explicit action.
|
|
153
153
|
|
|
@@ -1,18 +1,22 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: review-pull-request
|
|
3
|
-
description:
|
|
3
|
+
description: Review a GitHub pull request for merge conflicts, code defects, verification failures, and linked Xevy task coverage; post the full verdict as one PR comment by default unless the user opts out. Code, records, and merge behavior remain read-only.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Review a pull request
|
|
7
7
|
|
|
8
|
-
Review the exact PR and report evidence-based findings.
|
|
8
|
+
Review the exact PR and report evidence-based findings. Review remains **read-only for code, records, and merge**: do not edit source files, resolve conflicts, commit, push, submit a GitHub approval/change-request review, merge, deploy, or change Xevy records. There is exactly **one allowed mutation**: posting the full review summary as one new comment on the reviewed PR by default, unless the user explicitly says not to. Any other action requires separate authorization under its own workflow.
|
|
9
9
|
|
|
10
10
|
## 1. Identify the PR and working directory
|
|
11
11
|
|
|
12
|
+
- **Triage review depth first.** Inventory all changed files and affected flows, then classify each as focused (small, isolated, low-impact), standard (ordinary behavior change), or deep (security/auth, data integrity, payments/business decisions, concurrency/retries, migrations, deployment, broad refactors, or other critical paths). This adjusts effort, not coverage: account for every changed file and material flow; uncertain or high-impact areas receive deep review. Keep small PRs focused and avoid redundant historical or test work that cannot affect the verdict.
|
|
13
|
+
- **Keep a compact internal coverage ledger.** Track each changed file/flow, risk tier, reviewer/pass, evidence inspected or tested, and remaining gaps. Account for every changed file and requirement before the verdict. If material gaps mean the full changed scope cannot be reviewed, the verdict must be **MERGE SAFETY UNVERIFIED**. Keep the full ledger internal unless requested.
|
|
14
|
+
- **Parallelize when useful and supported.** For substantial PRs with separable behavior/risk areas and available independent reviewers, delegate disjoint scopes after pinning identical head/base SHAs and sharing task intent and conventions. Run independent safe checks concurrently where supported. Keep small PRs with one reviewer when coordination costs outweigh benefit. The lead owns the full inventory, confirms all delegated results arrived, reconciles disagreements against source evidence, and issues the verdict. Delegation never excuses skipped scope.
|
|
15
|
+
- **Add an omission-focused independent pass for substantial/high-risk reviews when available.** Give the second reviewer the pinned diff, requirements, changed-flow inventory, and ledger; ask them to find omissions, not merely confirm existing findings. Probe applicable error/recovery paths, authorization, concurrency/retries, partial data, and cross-component contracts. If unavailable or unwarranted, the lead performs an explicit gap pass and does not claim independent review.
|
|
12
16
|
- Accept a PR URL, number, or branch. If omitted, use the current branch's PR only when exactly one open PR matches; otherwise ask which PR.
|
|
13
17
|
- Identify the repository from the PR URL/metadata; do not ask the user to select a project directory or worktree when the PR uniquely identifies them. Ask only if repository identity is ambiguous or inaccessible.
|
|
14
18
|
- Review the PR's remote source and target branches, pinning their actual SHAs and merge-base. For required local verification, automatically locate an existing Git worktree where the PR source branch is checked out. Use that worktree only if it belongs to this PR/source branch and is safe to use; do not disrupt unrelated changes or another active task. If no suitable worktree exists, create a dedicated worktree for the PR source branch and record its path. Never ask the user which worktree to use. Do not switch branches in an existing checkout.
|
|
15
|
-
- Read the applicable `AGENTS.md` / `AGENTS.override.md` chain from the selected worktree. Keep
|
|
19
|
+
- Read the applicable `AGENTS.md` / `AGENTS.override.md` chain from the selected worktree. Keep inspection non-mutating: do not edit tracked files, commit, push, or merge. Only the final summary-comment step below may post a comment. Fetch/update remote refs as needed without altering another checkout. If the PR source branch is not available locally, fetch it and create the worktree at the exact reviewed head SHA; ensure the worktree represents the PR head, not a stale local branch.
|
|
16
20
|
- Testing is required. In the PR source worktree, run the repository's relevant focused tests and applicable lint, type-check, and build checks when feasible; include regression tests for suspected issues where practical. Avoid exposing secrets and do not run destructive commands. If dependencies, credentials, environment, or infrastructure prevent a check, report the exact limitation and mark that verification unverified; do not imply tests passed or issue an unqualified safe-to-merge verdict. Preserve pre-existing worktree changes and do not clean/reset them.
|
|
17
21
|
- Check whether this session is locked to a different task; do not switch its scope without the user's explicit approval under the session-lock rules.
|
|
18
22
|
- For a remote Dev Session, use `read_dev_session_pull_request` with the linked repository ID and PR number to read authenticated PR evidence; select the `dev_session` capability group if needed. Outside a session, use `code_pull_request` with the project and linked repository. Read `metadata`, then paginate `files`, `commits`, `reviews`, and `checks` until `nextPage` is null; inspect `diff` and every `truncated` flag. Use the returned top-level `headSha` and `baseSha` for current commit identity; `data.base.sha` retains GitHub's recorded PR base and can differ from the current target. Treat truncated or unavailable evidence as incomplete. Credentials stay in the toolbox; these tools require no `gh` login or token in the agent shell. If access is expired, ask the GitHub connection owner to reconnect and retry.
|
|
@@ -23,7 +27,7 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
|
|
|
23
27
|
|
|
24
28
|
- 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
29
|
- 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
|
-
- Inspect the full commit history contributing to the PR, not only the final diff or latest commit. Review commit messages
|
|
30
|
+
- Inspect the full commit history contributing to the PR, not only the final diff or latest commit. Review commit messages and identify task/scope references across the history. Inspect per-commit diffs and earlier versions to the depth needed to resolve intent, inherited/unrelated work, or regression origin; do not mechanically re-read historical diffs when they cannot change the current verdict. Compare the PR head to its current base for final behavior; history provides context and never excuses a defect in the final state.
|
|
27
31
|
- 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
32
|
- If no task is linked, review against the PR's stated objective and repository conventions. State that task-requirement coverage could not be assessed.
|
|
29
33
|
|
|
@@ -38,8 +42,8 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
|
|
|
38
42
|
- Investigate each suspected issue before reporting it: first establish intended behavior from the linked task and acceptance criteria, explicit decisions, PR description, design/spec documentation, and established surrounding behavior; then trace reachable callers, affected users/data, triggering conditions, existing guards, and consequences if left unfixed. Use a safe reproduction or test where feasible. Do not call an intentional change or omission a defect merely because a control, feature, behavior, or test is absent compared with the base branch. For example, a removed button is not a finding if its removal is required or explicitly intended. Report only behavior that conflicts with established intent or is an unintended consequence of the change as a confirmed finding. If intent is ambiguous or cannot be resolved, put it under **Warnings / Questions** with the missing evidence and potential impact; do not state it as a defect or release blocker. Classify each confirmed issue as **Release blocker** or **Non-blocking** independently of severity. A release blocker prevents a required flow, violates a critical task requirement, causes materially incorrect decisions, or creates significant security, data-integrity, or operational risk. Explain the concrete unfixed consequence; do not infer blocker status from severity alone. If reachability or impact cannot be established, report it under Questions/Risks with blocker status unverified, not as a confirmed blocker.
|
|
39
43
|
- Identify risky changes even when no defect is confirmed: destructive/bulk data operations; auth and permissions; financial or business-decision logic; API/integration contracts; jobs, retries and concurrency; deployment/configuration/dependencies; critical UI actions; broad refactors or unrelated/inherited scope. Assess affected users/data, reversibility, compatibility, test coverage, and recovery safeguards. Do not treat a risk category alone as a defect or release blocker; escalate only when evidence supports an unsafe condition, and mark material unresolved safety questions unverified.
|
|
40
44
|
- Build a risk-based test matrix from every changed behavior: expected outcome, counterexample, overlapping/multiple records, ordering, and relevant boundary conditions. Identify what was exercised by local tests or CI, what was assessed only by code inspection, and what remains unverified. Prioritize tests for high-impact paths over indiscriminate test runs. A passing test suite does not replace tracing untested combinations.
|
|
41
|
-
- On a repeat review, obtain the previous review report (ask the user for it if not accessible) and record its reviewed head/base SHAs, findings, coverage ledger, and unverified items. Recheck every previous finding and all changed lines since the earlier head,
|
|
42
|
-
- Run relevant tests, lint, type-check, and build checks only where safe in the permitted working directory; avoid commands that rewrite tracked files or require secrets. If not run, explain why. Separate PR-introduced failures from baseline/infrastructure failures where evidence supports it. Never claim there are no code issues solely because CI is green.
|
|
45
|
+
- On a repeat review, obtain the previous review report (ask the user for it if not accessible) and record its reviewed head/base SHAs, findings, coverage ledger, and unverified items. Recheck every previous finding and all changed lines since the earlier head, then repeat the full changed-file and affected-flow inventory; do not limit review to the fix diff. Reuse prior evidence only for unchanged files/flows when the head/base comparison, requirements, dependencies, interfaces, and relevant assumptions remain unchanged and the prior evidence is available. Reopen areas affected by the fix, a moved base, changed contracts, or assumptions; mark unavailable or stale coverage unverified. Never infer safety solely from unchanged lines. Attribute each new finding as introduced by later changes, exposed by a base change, pre-existing but missed, or unknown; do not claim regression origin without evidence.
|
|
46
|
+
- Run relevant tests, lint, type-check, and build checks only where safe in the permitted working directory; avoid commands that rewrite tracked files or require secrets. Select checks from the risk-based matrix, prioritize high-impact paths, and run independent checks concurrently when safe and supported. If not run, explain why. Separate PR-introduced failures from baseline/infrastructure failures where evidence supports it. Never claim there are no code issues solely because CI is green.
|
|
43
47
|
- Immediately before the verdict, re-read the PR's head and base SHAs. If either changed during review, refresh affected diff, mergeability, checks, and verification or mark the verdict stale/inconclusive; never present an earlier SHA's results as current.
|
|
44
48
|
|
|
45
49
|
## 4. Deliver a verdict
|
|
@@ -56,7 +60,19 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
|
|
|
56
60
|
- If multiple distinct tasks contribute changes to the PR, include **WARNING — Multiple tasks in this PR**, listing their identifiers, completion/verification status, and whether their inclusion is approved and necessary for the intended task. Explain briefly that unrelated or unfinished work would merge together. If additional work is suspected but task linkage cannot be established, label it suspected and state the missing evidence. Ask for clarification when scope approval is ambiguous; do not invent approval. Treat confirmed critical scope violations or unsafe unfinished behavior as blockers, and material unresolved scope/safety questions as unverified—not every multi-task PR as automatically unsafe.
|
|
57
61
|
- 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
62
|
- 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.
|
|
63
|
+
- For an optional process pilot/retrospective, record elapsed review time, later-confirmed missed issues, false positives, and unverified coverage across representative small and large PRs. Do not claim faster or more complete reviews without comparative evidence.
|
|
59
64
|
- 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
65
|
- 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
66
|
- 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
67
|
- 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.
|
|
68
|
+
|
|
69
|
+
## 5. Post the completed verdict as one PR comment
|
|
70
|
+
|
|
71
|
+
- **Always deliver the complete verdict in the user-facing conversation** on every completed review — when the comment posts successfully, when the user opts out, and when posting fails or is uncertain. The PR comment duplicates the verdict for GitHub readers; it never replaces the chat response. A comment-only reply without the verdict in conversation is a defect.
|
|
72
|
+
- Post **exactly one comment per completed review**, only after the complete verdict is established, unless the user explicitly says not to post. Never post mid-review or for aborted/inaccessible PRs. A completed review may report blockers or unverified checks; do not turn a posting failure into a favorable verdict.
|
|
73
|
+
- Render the full verdict from step 4 as one Markdown comment (headings and bullets, no tables), not just a teaser or link. Include the merge indicator and reviewed head/base SHAs, PR URL, every linked task code and freshly refreshed status (or Not linked/Unverified), the actual **Reviewed at:** timestamp, all findings and their **If not fixed:** and **Error if not fixed: Yes / No / Unverified** details, warnings, verification summary and limitations, and concise requirement coverage. End with the exact attribution footer: `🤖 Review generated by Xevy's review-pull-request skill`.
|
|
74
|
+
- On local checkouts with an existing authenticated `gh` login, verify the PR/repository identity and run `gh pr comment <PR> --body-file <tempfile>` in the PR's checkout. Use a private temporary UTF-8 file, not shell interpolation of verdict text; remove that temporary file afterwards. Do not expose credentials or request a new local login as a fallback from a Dev Session.
|
|
75
|
+
- In remote Dev Sessions use `comment_dev_session_pull_request` with sessionId, linked repositoryId, number, and body. Via Xevy CLI/MCP outside a session, use `comment_code_pull_request` with the project identifiers, linked repositoryId, number, and body. Select the `dev_session` or `repositories` capability group respectively if needed. These tools use Xevy's sealed GitHub connection and the session's pinned identity where applicable; no gh dependency, login, or token is needed in a Dev Session shell.
|
|
76
|
+
- Repeat reviews post a new comment: **never edit or delete previous comments**. Never post a second comment for the same completed review or automatically retry an uncertain write. If the request times out or returns an invalid receipt, inspect the PR for the comment first; do not claim success without a confirmed receipt or observed comment.
|
|
77
|
+
- If posting is unavailable or fails (including a missing toolbox endpoint, expired GitHub connection, insufficient write permission, or network error), still deliver the full verdict to the user and state exactly why the comment was not posted or why posting is unconfirmed. Include the comment URL on confirmed success; state when the user opted out. Do not silently drop findings, split into multiple comments, or fall back to editing old comments if the verdict exceeds the tool's 65536-character limit; report that posting limitation honestly.
|
|
78
|
+
- Include **no secrets or internal coverage ledgers in comments**. Never copy tokens, sealed credentials, environment values, private logs, or internal reviewer/coverage matrices into the body. The concise requirement coverage and verification summary belong in the verdict; internal ledgers do not.
|