gstack-opencode

Check local gstack setup health, detect stale build/setup state, and write a bounded upgrade-readiness report.

Interrogate an idea like a bounded YC-style office hours session and write a durable local memo.

Review recent local repository history and write a bounded engineering retrospective.

Prepare a local authenticated browser session for OpenCode QA and design workflows using gstack browse cookie import flows.

Audit a local rendered page with browser evidence, write a bounded design report, and optionally apply local UI fixes when explicitly requested.

Update a small, factual set of project docs from local changes and write a durable summary without committing or using GitHub APIs.

Run a structural pre-landing code review in OpenCode, write a durable local report, and optionally apply low-risk fixes when explicitly requested.

Prepare a branch for shipping by checking branch state, local tests, review readiness, and optionally carrying out explicit shipping actions.

Run browser-first QA in OpenCode, capture evidence, optionally fix local issues, and write a structured report.

Use gstack's persistent browser in OpenCode for screenshots, QA flows, console checks, and browser-driven verification.

Investigate a local reproducible bug, trace the likely root cause, and write a durable debug report without modifying code.

Propose a product design direction, separate safe choices from creative risks, and write a durable local report.

Review a product plan like a CEO/founder, challenge the premise, compare strategic approaches, and write a durable local report.

Review a product plan like a senior product designer, evaluate information architecture, interaction states, and AI slop risk, and write a durable local report.

Review an engineering plan, produce architecture and test guidance, and write a durable local report.

Run browser-first QA in OpenCode, capture evidence, and write a structured report without modifying source code or suggesting fixes.