菜单
Ensure a Linear ticket exists, then create and push a GitHub pull request for the latest commit — assigned to the author and linked so Linear auto-closes it. Use when the user runs /pull-request or asks to open a PR, create a pull request, push their branch as a PR, or "PR this".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Audit Waniwani event tracking across an MCP project. Does an in-depth overview check of the whole app (server, flows, tools, widgets, chat embed), verifies that only events defined in the Waniwani taxonomy are sent, and identifies missing events worth adding at each funnel stage (identify, lead_qualified, price_shown, prices_compared, option_selected, converted). Trigger when the user wants to audit tracking, check event coverage, find missing funnel events, verify events are valid, or review the instrumentation of an MCP built with @waniwani/sdk.
Auto-instrument Waniwani funnel events across a createFlow app. Analyzes every flow in the project, decides where each tracking event belongs (lead_qualified, price_shown, prices_compared, option_selected, converted, identify), inserts the calls with the right metadata from flow state, and verifies the result. Trigger when the user wants to add tracking to a flow, track qualified leads, instrument a funnel, measure conversions, or right after scaffolding a new flow with @waniwani/sdk.
MCP distribution SDK: build sales funnels, lead generation, booking flows, insurance quote flows, pricing quote flows, and any multi-step conversational MCP app with @waniwani/sdk. Open source createFlow engine (no API key required) with pluggable state backends (in-memory, Redis, Upstash, Cloudflare KV, DynamoDB, or hosted). Optional free tier adds a revenue-first event taxonomy (track leads, prices shown/compared, options selected, and conversions — including off-platform purchases), funnel analytics, knowledge base, and a chat widget. Trigger when the user wants to add an MCP funnel, sales funnel, lead gen flow, booking flow, quote flow, knowledge base / FAQ tool, or embedded chat to an MCP server — or to instrument tracking on a @waniwani/sdk app: emit or track events, record a conversion or revenue, attribute an off-platform purchase back to a lead, or measure where users drop off in a funnel.
Migrate a project from @waniwani/sdk 0.16.x to 0.17.0 and auto-apply its breaking change: useWaniwani() from @waniwani/sdk/mcp/react no longer auto-discovers its config from a WidgetProvider context or by opening its own host connection, so a bare useWaniwani() in a widget silently stops tracking. Skybridge widgets switch the import to @waniwani/sdk/mcp/react/skybridge; other hosts pass toolResponseMetadata or explicit { endpoint, source }. Trigger when the user is on @waniwani/sdk 0.16.x and wants to move to 0.17, asks to migrate to 0.17, or finds widget tracking silently stopped after bumping @waniwani/sdk to 0.17.
Migrate a project from @waniwani/sdk 0.17.x to 0.18.0 and auto-apply its breaking change: the generic funnel events quote.requested, quote.succeeded, quote.failed, and purchase.completed are removed from the track() taxonomy (with the QuoteSucceededProperties / PurchaseCompletedProperties types and the legacy quoteAmount / quoteCurrency / purchaseAmount / purchaseCurrency input fields). Call sites move to the typed revenue helpers track.priceShown() and track.converted(), or are deleted. Trigger when the user is on @waniwani/sdk 0.17.x and wants to move to 0.18, asks to migrate to 0.18, or hits type errors on quote.* / purchase.completed events after bumping @waniwani/sdk.
Cut a @waniwani/sdk version bump that ships its own migration path so users can upgrade automatically. Use when bumping the SDK version, releasing a breaking change, editing the changelog for a release, or when the user says "cut a release", "version bump", "ship a breaking change", or "prepare a migration".
| name | pull-request |
| description | Ensure a Linear ticket exists, then create and push a GitHub pull request for the latest commit — assigned to the author and linked so Linear auto-closes it. Use when the user runs /pull-request or asks to open a PR, create a pull request, push their branch as a PR, or "PR this". |
Create a GitHub pull request immediately using the following rules:
WAN-123) in the current branch name and in the latest commit message(s).assignee: "me" - this is the reliable team-safe way to assign to the current user. (Git/GitHub email may differ from the Linear email, so matching by email is unreliable; only fall back to list_users matching if "me" is unavailable.) Use list_teams to resolve the team."me".WAN-123) and its URL.assignee should be the current user); if it didn't, retry the assignment explicitly with save_issue.gh pr create --assignee @me to create the PR and auto-assign it to the user.WAN-123) either in the branch name or in the PR description body. If the ticket identifier is NOT already in the branch name, the PR body MUST contain a line Closes WAN-123 (using the real identifier). If it is already in the branch name, leave the body empty.Important: