glific

Take the current Glific frontend branch from local changes through green CI and addressed bot/reviewer comments, ready for human review. Runs tsc + prettier + Vitest + coverage locally, fixes the PR title to the required format, pushes, then polls Unit…

Diagnose and fix flaky/nondeterministic tests in the Glific frontend (Vitest + React Testing Library + Apollo MockedProvider, plus Cypress e2e). Reproduce intermittency, classify the root cause (real-timer/polling races, cross-file timer leakage, unflushed…

Make the current branch satisfy the Glific frontend Codecov gates (project + patch) by finding uncovered changed lines with Vitest/istanbul coverage and adding focused, behavior-asserting tests until green. Use when the user asks to improve coverage, fix a…

Review the current branch / PR diff for the glific-frontend codebase against its React 19 + TypeScript + Apollo conventions. Use before opening or merging a PR, or when asked to review frontend changes.

Prepare the current branch for PR review in Glific: run MIX_ENV=test mix check and tests, meet Codecov thresholds, self-review, commit, push, then poll CI/Codecov/CodeRabbit until green. Use when the user asks to make a branch review-ready, get changes ready…

Diagnose and fix flaky tests in Glific by reproducing intermittency, isolating ordering and global-mock conflicts, applying the smallest safe fix, and verifying stability with repeated targeted and suite runs. Use when the user reports flaky or…

Check whether branch changes meet Glific Codecov thresholds using only local git and ExCoveralls (no push, no CODECOV_TOKEN), add focused tests for gaps, and re-run until the local gate passes. Use when the user asks to improve coverage, fix Codecov failures,…

Prepare the current branch for remote push: verify compile/lint/format, loop code-reviewer-claude and code-reviewer-coderabbit in sequence (identify feedback, fix low criticality, confirm high with user), commit and push. Never creates a new local branch.

Generate, update, or review Glific user-facing documentation. Use when a developer asks to document a feature, write a doc page, update existing docs, or after a PR ships to refresh affected docs.