Problem
What problem this solves
Technical checks and verification can pass while nobody has actually walked through the user-facing flow in the app.
Menu Open navigation menu Close navigation menu
Build & Fix Featured
Skill Detail
sg-test
Guide the human through the real user flow, then turn the result into test evidence and actionable bugs.
A manual QA skill for creating guided test campaigns, capturing structured outcomes, and preserving bug history after implementation.
Outcome
What changes when it works
You get a concrete manual test protocol, compact test and bug indexes, and durable bug dossiers with separated evidence.
Why It Matters
What this changes for a solo founder
This skill matters because finished code is not the same thing as a tested user journey. It gives the founder a clear script to follow and turns every failure into an actionable record without bloating the trackers.
When to use it
- After implementation and verification, before shipping
- When the work changes a visible user flow
- When login, onboarding, protected routes, uploads, payments, or redirects need real observation
- After a fix, when the original bug needs a precise retest
What you give it
- The recent feature, task, or spec to test
- The target environment: local, preview, or production
- Optional context such as a bug id, route, account type, or user flow
What you get back
- Step-by-step manual test instructions
- Structured result choices for common failure modes
- A compact shipglows_data/workflow/TEST_LOG.md record for the campaign
- A compact shipglows_data/workflow/BUGS.md index entry when the test fails
- A per-bug dossier under shipglows_data/workflow/bugs/BUG-ID.md
- Redacted evidence references under test-evidence/BUG-ID/ when needed
- A route into sg-browser when a narrow non-auth browser check is enough
- A clean route into sg-fix or sg-auth-debug when the failure needs diagnosis
Typical examples
- /sg-test
- /sg-test Google Auth
- /sg-test --retest BUG-2026-04-26-001
- /sg-test --prod onboarding flow
Limits
- It guides and records manual evidence; it does not replace automated tests
- It must stay anchored to the spec, recent diff, acceptance criteria, or verification findings
Related Skills
See the rest of the loop around this move.
Operate & Ship
sg-check
Run the standard technical checks and fix the obvious issues before you pretend the work is done.
A practical quality gate for typecheck, lint, build, and related technical validation in the current project.
Open skill page Audit & Improve
sg-verify
Check whether the work really satisfies the user story, not just whether the code compiles.
A verification skill for standard readiness or an explicit excellence-focused second pass beyond the task's acceptance criteria.
Open skill page Build & Fix
sg-bug
Run a bug from report to dossier, fix, retest, verification, and ship risk without skipping gates.
A professional bug loop executor that reads bug state and continues through the right ShipGlows owner skills when safe.
Open skill page Build & Fix
sg-browser
Open a URL in a real browser and verify one observable non-auth objective.
A general browser verification skill for checking public UI, previews, production pages, visible assertions, screenshots, console messages, and network signals without turning every page check into auth debugging or manual QA.
Open skill page Build & Fix
sg-auth-debug
Debug a broken auth flow in a real browser before you start guessing from static code alone.
A browser-level auth diagnosis skill for reproducing login failures, reading local Clerk/Google/Convex/Flutter references, and isolating the exact break point in the flow.
Open skill page Build & Fix
sg-fix
Triage a bug fast, decide whether it is safe to patch now, and route it correctly.
The bug-first entrypoint for ShipGlows when the work starts from broken behavior instead of a new feature request.
Open skill page Operate & Ship
sg-ship
Commit and push quickly when the work is actually ready, instead of stretching closure into another vague step.
A shipping skill for moving finished work through the final commit-and-push path and recording the shipping result when a chantier spec is in scope.
Open skill pageGo Deeper
This public page explains the move. The repository explains the execution contract.
Use the public catalog for education and workflow selection. Move to the docs and GitHub when you want the operator-grade execution details behind the skill system.