@xevy/skills 0.1.67 → 0.1.69
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.69",
|
|
6
6
|
"author": {
|
|
7
7
|
"name": "Xevy"
|
|
8
8
|
},
|
package/package.json
CHANGED
package/skills/deploy/SKILL.md
CHANGED
|
@@ -1,26 +1,42 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: deploy
|
|
3
|
-
description: Deploy a
|
|
4
|
-
argument-hint: "[preview|main] [task]"
|
|
3
|
+
description: Deploy a task preview, the shared staging/development environment, or an explicitly registered production application through Xevy. Confirm production by its saved destination and report the deployment's actual outcome.
|
|
4
|
+
argument-hint: "[preview|main|production] [task or repository]"
|
|
5
5
|
disable-model-invocation: true
|
|
6
|
-
allowed-tools: "Read Bash mcp__xevy__deploy_preview mcp__xevy__deploy_main mcp__xevy__get_deploy_status mcp__xevy__find_task"
|
|
6
|
+
allowed-tools: "Read Bash mcp__xevy__deploy_preview mcp__xevy__deploy_main mcp__xevy__get_deploy_status mcp__xevy__find_task mcp__xevy__list_repositories mcp__xevy__project_deployment_target mcp__xevy__project_deployment_redeploy mcp__xevy__project_deployments_list mcp__xevy__project_deployment_logs"
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
-
# /xevy:deploy — deploy a preview or
|
|
9
|
+
# /xevy:deploy — deploy a preview, staging or production application
|
|
10
10
|
|
|
11
|
-
|
|
11
|
+
Resolve the requested environment and repository, confirm the consequential action, then follow the build to its recorded outcome. Deployment authorization and PR-merge authorization are separate actions.
|
|
12
12
|
|
|
13
13
|
## Resolve target
|
|
14
|
-
-
|
|
14
|
+
- `preview` selects a per-task preview. `main` selects shared staging/development. `production` selects the repository's explicitly registered production application. With no environment supplied, use a task preview when a task is in context and shared staging/development otherwise. Preserve an explicit production request throughout the workflow.
|
|
15
|
+
- Resolve repository identity from the session, linked task or `list_repositories`. Ask when multiple repositories remain plausible. Branch names, hostnames and provider UUIDs from chat do not establish a production target.
|
|
16
|
+
- In a Dev Session, activate `repositories` capabilities to discover `project_deployment_target`, `project_deployment_redeploy`, `project_deployments_list` and `project_deployment_logs`. These use Xevy's authenticated service path; provider credentials stay outside the agent shell.
|
|
15
17
|
|
|
16
18
|
## Preview
|
|
17
19
|
- Resolve the task (`mcp__xevy__find_task` by code). A pushed feature branch must exist. Call `mcp__xevy__deploy_preview({ taskId })` using recorded evidence, or optionally supply its exact pushed `branch` when not yet recorded. Conflicting branch input is rejected; never rewrite repository identity to force deployment.
|
|
18
20
|
- Association is automatic: branch-only legacy tasks check linked deployment-enabled repositories; existing scoped records and exclusions remain authoritative. No repository selector is required. Every selected branch must be verified exactly; absent branches, inaccessible repositories, missing credentials or unavailable verification are skipped. Never substitute a default branch.
|
|
19
21
|
- Report actual `queued`, `partial` or `skipped` status, URLs and each repository's reason. Partial results mean only independently verified repositories queued. If nothing queued, do not claim a build started; explain the recorded reasons.
|
|
20
22
|
|
|
21
|
-
## Main
|
|
22
|
-
-
|
|
23
|
+
## Main: shared staging/development
|
|
24
|
+
- Obtain approval for shared staging/development, then call `mcp__xevy__deploy_main` for the current project. It deploys the project's REMOTE default branch. Local changes become available after their PR lands remotely. Report the main URL and follow it with `get_deploy_status`. Production requests use the production workflow below.
|
|
25
|
+
|
|
26
|
+
## Production
|
|
27
|
+
|
|
28
|
+
1. Confirm the requested repository and production release are authorized. If merging is needed, complete the separately approved PR merge and verify its remote receipt first.
|
|
29
|
+
2. Call `project_deployment_target` with the selected project, `repositoryId` and `environment: "production"`. Read the saved application name, `canRedeploy` and opaque `confirmTarget`.
|
|
30
|
+
3. Obtain approval for this exact production destination. The primary Dev Session shows the production application and target confirmation. Nested agents return release actions to the primary session. An earlier blanket approval for other work does not approve this destination.
|
|
31
|
+
4. Call `project_deployment_redeploy` with the same scope, `environment: "production"`, the exact application name as `confirmName`, and the returned `confirmTarget`. A changed destination requires a fresh lookup and approval.
|
|
32
|
+
5. Follow the returned deployment with `project_deployments_list`; use `project_deployment_logs` for bounded diagnostics. A queued response confirms dispatch. Report completion when that deployment reaches `succeeded` and any available application health check passes. Report `failed` and `cancelled` outcomes accurately.
|
|
33
|
+
|
|
34
|
+
- `target_missing` requires restoring the verified production link to the existing application before deployment. Report the missing registration and continue independent authorized work.
|
|
35
|
+
- `destination_read_only` means the registered connector supports reads. `hosting_forbidden` means the saved provider scope cannot manage the resource. Report the specific access requirement and preserve the existing scope boundaries.
|
|
36
|
+
- An unavailable deployment receipt leaves dispatch uncertain. Inspect recent deployments before retrying. `deployment_busy` requires following the active build before another request.
|
|
37
|
+
- Production deployment uses the existing registered application. Provisioning replacements, changing configuration or ENV, restarting supporting services and bypassing ownership checks require their own authorized workflows.
|
|
23
38
|
|
|
24
39
|
## Report progress
|
|
25
|
-
-
|
|
40
|
+
- Preview and shared staging/development deploys use `get_deploy_status`. Production uses `project_deployments_list` and `project_deployment_logs`. A queued or running build remains open until its terminal outcome or a stated observation/access limit.
|
|
41
|
+
- Give the repository, environment, deployment ID and actual state. Include the URL when the service returns one. Separate successful dispatch from application verification.
|
|
26
42
|
- If the server reports previews are disabled, say so and stop. Never push protected branches (master/main/develop/staging) to make a deploy reflect local changes.
|
|
@@ -3,7 +3,7 @@ name: merge-pull-request
|
|
|
3
3
|
description: Evaluate a GitHub pull request, repair merge conflicts and PR-caused failures on its head branch, verify it, and merge it when ready. Use whenever the user asks to review and merge a PR, resolve a PR conflict before merging, or replace the former merge --cloud workflow. Raise remaining issues and blockers with evidence, then ask whether to create Xevy tasks or explicitly disregard them before proceeding.
|
|
4
4
|
argument-hint: "[pull-request URL|number|branch]"
|
|
5
5
|
disable-model-invocation: true
|
|
6
|
-
allowed-tools: "Read Grep Edit Bash mcp__xevy__find_task mcp__xevy__list_tasks mcp__xevy__get_project_workbreakdown mcp__xevy__create_task"
|
|
6
|
+
allowed-tools: "Read Grep Edit Bash mcp__xevy__find_task mcp__xevy__list_tasks mcp__xevy__get_project_workbreakdown mcp__xevy__create_task mcp__xevy__read_dev_session_pull_request mcp__xevy__prepare_dev_session_pull_request_review mcp__xevy__merge_dev_session_pull_request mcp__xevy__list_dev_session_branches mcp__xevy__push_dev_session_branch"
|
|
7
7
|
---
|
|
8
8
|
|
|
9
9
|
# /xevy:merge-pull-request — evaluate, repair, and merge a pull request
|
|
@@ -13,14 +13,16 @@ Review the exact pull request, repair merge conflicts and PR-caused failures on
|
|
|
13
13
|
## 1. Resolve the pull request
|
|
14
14
|
|
|
15
15
|
- Resolve `$ARGUMENTS` as a GitHub pull-request URL, pull-request number, or head branch. When it is empty, use the pull request associated with the current branch only when exactly one open pull request matches.
|
|
16
|
-
-
|
|
17
|
-
-
|
|
16
|
+
- In a Dev Session, activate the `dev_session` capability group and use `read_dev_session_pull_request` with the linked `repositoryId` and PR number. Read metadata, files, commits, reviews and checks; follow every `nextPage` and treat `truncated` as incomplete evidence. The session's pinned GitHub connection stays inside the toolbox; shell GitHub authentication is unnecessary.
|
|
17
|
+
- Save `headSha`, the current `baseSha`, and the base branch from fresh metadata. `data.base.sha` may describe an older recorded base; use the top-level `baseSha` for the current target tip.
|
|
18
|
+
- On a workstation, verify GitHub CLI authentication and repository identity before making changes. Read the pull request with `gh pr view`, including its number, URL, state, draft state, head and base branches, mergeability, merge-state status, review decision, checks, commits, and changed files.
|
|
18
19
|
- Stop with a clear blocker when the pull request is closed, already merged, missing, or belongs to a different repository than the checkout.
|
|
19
20
|
- Record the exact head repository and branch. Repairs belong on the pull-request head branch; protected base branches receive changes through the pull request.
|
|
20
21
|
|
|
21
22
|
## 2. Evaluate the change
|
|
22
23
|
|
|
23
24
|
- Fetch the base and head refs, inspect the complete pull-request diff, and read the relevant callers, tests, migrations, configuration, and established patterns.
|
|
25
|
+
- In a Dev Session, use `prepare_dev_session_pull_request_review` to obtain a detached checkout of the exact PR head and current base. Run verification in its returned directory. Reconcile the returned SHAs with the reviewed evidence before continuing.
|
|
24
26
|
- Check the pull request against its stated goal and repository instructions. Focus on correctness, security, data integrity, backward compatibility, operational safety, and test coverage.
|
|
25
27
|
- 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
28
|
- Inspect required GitHub checks, requested reviews, branch protection, draft state, and merge queue requirements.
|
|
@@ -36,6 +38,7 @@ Review the exact pull request, repair merge conflicts and PR-caused failures on
|
|
|
36
38
|
- Repair verification failures introduced by the pull request or by the conflict resolution when the fix is clear and stays within the pull request's scope.
|
|
37
39
|
- Pause for a product decision when a conflict has multiple valid outcomes with materially different behavior.
|
|
38
40
|
- Stage and commit the repairs with an evidence-based message, then push the pull-request head branch. Never push a protected base branch directly.
|
|
41
|
+
- In a Dev Session, repair in a registered worktree matching the PR's head branch and publish through `push_dev_session_branch`. A detached review checkout is for verification. If the head branch cannot be published through the session's registered branch authority, report that limitation before attempting a repair push.
|
|
39
42
|
- Rerun affected local checks and refresh the GitHub pull-request state after the push. Wait for required checks through GitHub's supported check-watching command when they are running.
|
|
40
43
|
|
|
41
44
|
## 4. Handle remaining findings
|
|
@@ -60,8 +63,11 @@ Review the exact pull request, repair merge conflicts and PR-caused failures on
|
|
|
60
63
|
|
|
61
64
|
- Refresh the pull-request state immediately before merging. A ready pull request is open, non-draft, conflict-free, free of unresolved blockers, and compliant with required checks and repository protection.
|
|
62
65
|
- Follow the repository's established merge method. Infer it from repository settings and recent merged pull requests; use squash when the repository permits multiple methods and no convention is evident.
|
|
63
|
-
-
|
|
66
|
+
- In a Dev Session, call `merge_dev_session_pull_request` with the session repository, PR number, `expectedHeadSha`, `expectedBaseBranch`, `expectedBaseSha`, and selected `mergeMethod`. Use the exact reviewed head and current base evidence. The primary session requests approval for this specific merge; nested agents return the action to the primary session.
|
|
67
|
+
- If the head, base branch or current base tip changed, refresh the PR and review the affected changes before obtaining fresh approval. Pending or failed checks, unresolved mergeability and GitHub protections remain release gates. Credentials stay inside the toolbox.
|
|
68
|
+
- Merge with `gh pr merge` on a workstation and keep branch deletion separate from this command. Use the reviewed head SHA with the CLI's matching-head option when available.
|
|
64
69
|
- Confirm the remote pull request reports a merged timestamp and merge commit. Report the pull-request URL, merge method, commit, repaired conflicts, verification results, and any approved disregards or follow-up issues.
|
|
70
|
+
- An unavailable merge receipt leaves the outcome uncertain. Read the PR before retrying; a timed-out request may have completed. An already-merged receipt confirms existing state without another merge request.
|
|
65
71
|
|
|
66
72
|
## Boundaries
|
|
67
73
|
|
|
@@ -68,6 +68,7 @@ Review the exact PR and report evidence-based findings. Review remains **read-on
|
|
|
68
68
|
|
|
69
69
|
## 5. Post the completed verdict as one PR comment
|
|
70
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.
|
|
71
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.
|
|
72
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`.
|
|
73
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.
|