菜单
Draft PRs with trailing " - W-XXXXXXXX" in titles, conventional commit-style before it, GUS refs in body. Use when drafting PRs, PR titles, PR descriptions, opening PRs, or Git2Gus workflows.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Enforces Effect-TS patterns for services, errors, layers, and atoms. Use when writing code with Effect.Service, Schema.TaggedError, Layer composition, or effect-atom React components.
Consume the salesforcedx-vscode-services extension API. Use when an extension depends on salesforcedx-vscode-services and you are registering commands, calling its services (Workspace, Connection, Project, Settings, FS, Channel, Media, prompts), watching files/config/target-org, or wiring the AllServicesLayer/runtime in extensionProvider.ts.
package.json conventions for this repo. Use when editing/reviewing a package.json — name, types, browser, files, dependencies, devDependencies, packaging, scripts, or vscode contributes.
Prefer vscode-uri over node:path. Use when .ts files in /src import node:path or use path.join/basename/dirname/resolve, URI.file, or memfs paths.
Add custom SVG icons to salesforcedx-vscode-services for font generation. Use when adding new icons to media/icons-src, creating SVG icons for VS Code extension, or defining font-based icons.
TypeScript coding standards — apply when writing, reviewing, or refactoring .ts/.tsx, or naming/renaming .ts files (camelCase casing).
| name | pr-draft |
| description | Draft PRs with trailing " - W-XXXXXXXX" in titles, conventional commit-style before it, GUS refs in body. Use when drafting PRs, PR titles, PR descriptions, opening PRs, or Git2Gus workflows. |
Draft PR titles and bodies per salesforcedx-vscode conventions. Requires a Gus work item number.
Confirmation required: Never create or update work items without explicit user confirmation. Present proposed fields (Subject, Epic, Details, etc.) and wait for user to approve before any sf data create record or sf data update record.
Safety never use --no-verify
W-XXXXX, confirm it exists in GUS, resembles the work done on the branch, and use thatsf data create record until user says yes. If user declines creation and still wants to proceed with the PR, include [skip-validate-pr] in the PR body.git push -u origin $(git branch --show-current) or equivalent). Never push to develop/mainDetails__c with PR link. Query current Details__c, append "\nPR: <url>" (or prepend if empty). Before updating: show user the new Details__c. Ask: "Update work item with PR link?" Do not run sf data update record until user says yes.developgit reflog show <branch> | tail -1 → "moving from X" / "Created from X"main; inferred main → developtype(scope): description - W-XXXXXXXX
Name ( - W-21735053). This is the Name field from GUS, not the Salesforce Record ID (e.g., a07...). If you just created the record, query the Name first.build(extensions): consolidate apex-tmlanguage - W-21735053[W-21735053] build(extensions): …; bare trailing WI without - — build(extensions): … W-21735053Before finalizing body, fetch and analyze:
gh issue list --state open --limit 200 --json number,title,body,commentsgh api graphql — fetch all open discussions (title, number, url, body)W-12345) — no prompt needed; Git2Gus already established the linkDetails__c: SF empties external hrefs on save (the why + stored forms live in gus-cli), leaving <a href="">discussions/NNN</a> — text survives, href empty. Scan Details__c for such anchors with discussions/NNN|issues/NNN text, EXCLUDE anchors with a populated real href, and auto-include the reconstructed https://github.com/forcedotcom/salesforcedx-vscode/<path> URL — no prompt.#<number>, discussions as full URL — both in the "What issues does this PR fix or reference?" section@W-XXXXX@ in "What issues does this PR fix or reference?" per .github/PULL_REQUEST_TEMPLATE.md:[skip-validate-pr] in body (e.g. at end)### What issues does this PR fix or reference?
#<GitHub Issue>, @W-XXXXX@