Commits and pushes using this repo's scope prefixes (Participant, Researcher, Both, None). Makes one commit per logical change; optionally writes changelog JSON. When this skill is invoked, run git push at the end without asking—the user has authorized the push.
When helping with commit or push in this repo:
git push once — do not ask for permission; the user has invoked this skill to push.node scripts/get-latest-changelog-version.mjs (from repo root; requires .env or .env.local with VITE_SUPABASE_URL and VITE_SUPABASE_PUBLISHABLE_KEY). The script reads the max version from changelog_entries and prints it to stdout — use that as the current version. If the script fails (missing env, no DB access, or script not found), fall back to inferring from the latest docs/changelog-import-*.json filename (e.g. changelog-import-2026-02-11-1.1.5-4.json → version 1.1.5). For the next batch filename use the same version and the next batch number (e.g. changelog-import-YYYY-MM-DD-1.8-1.json, then -2.json, …).version (current version), release_date (today, YYYY-MM-DD), description (short summary of this batch), active_batch_label (optional), changes (array of one object per commit: type = added|changed|fixed|removed, description = first line of commit message without prefix, scope = participant|researcher|both from the commit prefix, commit_hash = short hash). Use a unique filename so the app imports it, e.g. docs/changelog-import-YYYY-MM-DD-VERSION-N.json (e.g. changelog-import-2026-02-11-1.1.5-1.json, -2.json, …) or include a short timestamp. Same JSON shape as in docs/changelog-import-*.json (array of one entry with version, release_date, description, changes). Commit the new file, then run git push.| Prefix | Use for |
|---|---|
| Participant | What participants see or do: consent, no-consent, questionnaires (PETS, TIAS, Godspeed, TIPI, demographics), feedback UI, practice flow, mic permission/UX, progress bar, alternating mode UI. |
| Researcher | Researcher-only: changelog, batches, response details, time analysis, table/CSV/filters, prompts lab, formality/stats tools, researcher auth, TIPI/batch display, Vapi debug. |
| Both | Clearly touches both participant and researcher surfaces; use only when it really applies. |
| None | No user-facing impact: tooling, CI, docs, deps, refactors without behavior change. |
Guidance: Prefer the most specific scope (Participant or Researcher); use Both only when the change really affects both.
Map commit prefix to changelog scope: Participant → participant, Researcher → researcher, Both → both, None → researcher (or both if it affects both).
Participant: change PETS survey titleResearcher: add batch filter to changelogBoth: rename token_used to is_completedNone: bump deps / update README