Sessions to shipped fixes
A recorded user-testing session carries issues, network failures and console errors. These three skills turn that into changed code and maintained tests.
/vitrinka:sessions
The autopilot. It discovers this project's unprocessed recorded sessions and drives each one through the whole pipeline — fix, then generate tests, then record what was done.
/vitrinka:session-fix
Turns one recorded session into shipped fixes. It reads the session once through the digest rather than repeatedly, then groups its issues — annotations, network failures and console errors together — into blocks of 5–10 related problems.
/vitrinka:generate-test
Turns a recorded session into maintained end-to-end journey tests, in the runner the project actually uses.
- Runner auto-detected — Playwright for web, Appium/WebdriverIO for Expo and React Native.
- Consolidation verdicts — each journey is judged against the existing registry — extend, update, new, or skip — so a re-recorded flow does not fork into a duplicate suite.
- Recorded — the outcome lands in
.vitrinka/journeys.jsonandsessions.json.