@xevy/skills 0.1.61 → 0.1.62
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.62",
|
|
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.
|
|
141
|
+
The package version is `0.1.62`. Run `npx @xevy/skills update -y` after that version is published.
|
|
142
142
|
|
|
143
143
|
## Security
|
|
144
144
|
|
package/package.json
CHANGED
|
@@ -10,13 +10,14 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
|
|
|
10
10
|
## 1. Identify the PR and working directory
|
|
11
11
|
|
|
12
12
|
- 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
|
-
- Resolve only enough repository/task metadata to suggest a directory. **Before any project-scoped inspection or workflow action, ask the user to confirm the project directory**, offering likely choices. Do not inspect project files or run project commands until confirmed.
|
|
14
13
|
- 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.
|
|
15
14
|
- 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.
|
|
16
15
|
- Read the applicable `AGENTS.md` / `AGENTS.override.md` chain from the selected worktree. Keep review actions non-mutating: do not edit tracked files, commit, push, post comments, or merge. 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.
|
|
17
16
|
- 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.
|
|
18
17
|
- 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.
|
|
19
|
-
-
|
|
18
|
+
- 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.
|
|
19
|
+
- For local verification in a remote Dev Session, use `prepare_dev_session_pull_request_review` with that repository ID and PR number. It fetches the exact PR head and current target into a fresh detached checkout and returns `dir`, `headSha`, `baseSha`, and `mergeBaseSha`. Run inspection and tests in `/workspace/<dir>`; preserve the original session checkout. The PR target comes from GitHub metadata and can differ from the session's configured base. Follow the returned evidence and report any incomplete fetch or history.
|
|
20
|
+
- On a local checkout outside a remote Dev Session, verify `gh` authentication before using it. Verify the checkout's repository identity and that the PR belongs to that repository. Read the PR URL, number, state, draft status, head/base repositories and branches, head SHA, review status, mergeability, checks, commits, and changed files. Stop if missing, closed, or already merged.
|
|
20
21
|
|
|
21
22
|
## 2. Establish task intent (when linked)
|
|
22
23
|
|
|
@@ -28,7 +29,7 @@ Review the exact PR and report evidence-based findings. This skill is **read-onl
|
|
|
28
29
|
|
|
29
30
|
## 3. Inspect mergeability and implementation
|
|
30
31
|
|
|
31
|
-
- Fetch current remote base and head refs without altering the checked-out branch. Pin and report both **actual fetched commit SHAs**, the merge-base SHA, and the diff range used; do not substitute the PR's original/recorded base for its current target. If the base moves, reassess the resulting diff and mergeability before concluding.
|
|
32
|
+
- Fetch current remote base and head refs without altering the checked-out branch. Pin and report both **actual fetched commit SHAs**, the merge-base SHA, and the diff range used; do not substitute the PR's original/recorded base for its current target. If the base moves, reassess the resulting diff and mergeability before concluding. In the prepared checkout, use `git diff <mergeBaseSha> <headSha>` as the authoritative current comparison. GitHub's files, commits, and diff sections describe its PR view and can reflect the recorded base; use the pinned current target for the merge simulation below.
|
|
32
33
|
- Enumerate every changed file and affected user flow before judging any finding. Inspect the complete PR diff, relevant callers, tests, interfaces, migrations, configuration, and affected workflows. Maintain a coverage ledger for each changed file/flow: reviewed logic, relevant tests, and any uninspected region with its reason. Do not stop review after finding the first blocker or an apparent fix; finish the full inventory.
|
|
33
34
|
- For each changed decision path, trace inputs through selection, filtering, aggregation, attribution, presentation, and export. Check positive/negative cases, multiple candidate records, ordering, unrelated-but-plausible records, missing/partial data, authorization, and state changes where applicable. Check that a predicate used to justify an outcome belongs to the *same record* named in the outcome. Mark irrelevant cases not applicable rather than skipping the checklist silently.
|
|
34
35
|
- Check GitHub's `mergeable` / `mergeStateStatus` and required checks. If GitHub reports `UNKNOWN`, re-query when feasible; distinguish unknown from a confirmed conflict.
|