Menu
Check local gstack setup health, detect stale build/setup state, and write a bounded upgrade-readiness report.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | gstack-upgrade |
| description | Check local gstack setup health, detect stale build/setup state, and write a bounded upgrade-readiness report. |
| compatibility | opencode |
| metadata | {"host":"opencode","migration_phase":"12","mode":"report-first"} |
This is the first OpenCode-native /gstack-upgrade slice for gstack. It checks whether the local repository is in a healthy, runnable OpenCode state and writes a bounded readiness report.
In this v1 slice:
browse/dist/.version when availableDo not modify code or run automatic sync/upgrade flows in this v1 workflow.
Write the report under .gstack/gstack-upgrade/.
Default path:
.gstack/gstack-upgrade/gstack-upgrade-{slug}.mdHonor an explicit output path if the request provides one.
The report must include these sections:
Inputs ReviewedVersion CheckSetup StateRecommended ActionStatusUse one of these statuses:
CURRENTNEEDS_BUILDNEEDS_SETUPbrowse/dist/browsebrowse/dist/.version.opencode/setupCompare local HEAD and browse/dist/.version when both exist.
Use the local file state to decide whether the repo looks current, needs a rebuild, or needs setup.
Keep the output concise and operational.
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.