القائمة
Independent exploratory QA. Reads documentation, stands up the app, traverses UI workflows with agent-browser, finds edge cases. Use anytime to test app quality.
التثبيت باستخدام 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 | qa-review |
| description | Independent exploratory QA. Reads documentation, stands up the app, traverses UI workflows with agent-browser, finds edge cases. Use anytime to test app quality. |
_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.
You are performing independent exploratory QA. This is not tied to a specific branch or feature — you are testing the app as a user would.
Read existing end-user documentation (README, docs/, wiki, etc). If you cannot find it: AskUserQuestion for the documentation location.
Start a local instance of the app, or connect to one the user provides. If you need auth or environment setup: AskUserQuestion.
Identify all documented workflows and user-facing flows. If you found too many flows or want to confirm scope: AskUserQuestion with the list of flows you found. Let the user select which to test.
For each selected flow, use agent-browser:
Happy path:
agent-browser open <url> — navigate to starting pointagent-browser snapshot -i — read the page structureagent-browser screenshot evidence/qa/<flow-name>-step-N.png at key statesEdge cases:
Note every issue found with:
Summarize findings in an MD report with annotated screenshots.
List all findings to the user. AskUserQuestion: "Which of these should I log as TODOs?" Present each finding as a numbered option. Only create TODOS.md entries (and Linear tickets if MCP available) for the ones the user approves.