菜单
Check and install prerequisites for upstack. Verifies git, gh, agent-browser, and skill symlinks. Use when first setting up or troubleshooting.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Ship a feature branch: write docs, bump version, create PR with screenshots and evidence. Links Linear tickets if available. Use when ready to merge.
Functional verification against the plan. Manually confirms every planned path works, takes screenshots, saves API examples as evidence for the PR. Use after /execute.
Build a plan to spec using Red/Green TDD. Writes tests first, confirms they fail, then implements. Supports --ticket mode for scoped execution with dependency checks and file-level scope guardrails. Use after /plan to implement a feature or fix.
Plan a feature or bug fix with deep engineering analysis. Explores the codebase, compares implementation alternatives, maps error paths, and produces test coverage diagrams — all before any code is written. Emits structured YAML tickets with dependency DAG and self-contained agent briefs. Optionally materializes to Linear and TODOS.md. Use when starting new work, breaking down a feature, or before any code changes. Strongly recommended as the first step before /execute.
Full sprint flow: /plan -> /execute -> /validate -> /review -> /ship-pr. Always runs /plan (which auto-detects small follow-ups via fast-path). Loops review/execute until clean. End result is a pushed PR.
Analyzes git state, TODOs, and project context to recommend which upstack skill to run next. Use when starting a session or unsure what to do.
| name | setup |
| description | Check and install prerequisites for upstack. Verifies git, gh, agent-browser, and skill symlinks. Use when first setting up or troubleshooting. |
| disable-model-invocation | true |
_UPD=$(~/.claude/skills/upstack/bin/upstack-update-check 2>/dev/null || .claude/skills/upstack/bin/upstack-update-check 2>/dev/null || true)
[ -n "$_UPD" ] && echo "$_UPD" || true
If output shows UPGRADE_AVAILABLE <old> <new>: read ~/.claude/skills/upstack/skills/upgrade/SKILL.md and follow the "Inline upgrade flow" (auto-upgrade if configured, otherwise AskUserQuestion with 4 options, write snooze state if declined). If JUST_UPGRADED <from> <to>: tell user "Running upstack v{to} (just updated!)" and continue.
Run checks silently, then report a summary table:
| Tool | Check | Required By |
|---|---|---|
| git | git --version | all skills |
| gh | gh --version | /ship-pr, /review, /advisor |
| gh auth | gh auth status | /ship-pr, /review, /advisor |
| agent-browser | agent-browser --version | /plan, /execute, /validate, /qa-review |
| node | node --version | /validate (JS projects) |
| python | python3 --version | /validate (Python projects) |
Print table with status for each tool. Mark required tools vs optional.
If required tools are missing, AskUserQuestion: "Missing: [list]. Should I show install commands?"
Install commands (never run automatically). Detect OS for appropriate package manager:
gh (https://cli.github.com/):
brew install gh then gh auth loginsudo dnf install gh then gh auth loginwinget install --id GitHub.cli then gh auth loginagent-browser by Vercel (https://github.com/vercel-labs/agent-browser):
brew install agent-browser then agent-browser installnpm install -g agent-browser then agent-browser install (requires Node.js)List all skills in ~/.claude/skills/ that point to the upstack repo.
Report any broken or missing symlinks.
If symlinks are broken: suggest re-running install.sh.
If user mentions Linear: check for Linear MCP server configuration. Explain which skills benefit (plan, advisor, ship) and how to set it up.