dimagi

Use when creating, opening, or submitting a pull request in a Dimagi mobile/CommCare repo — identified by JIRA-prefixed branches (e.g. CCCT-1929-...), a `RELEASES.md` with `### Release Notes` and `### QA Notes` sections, and the dimagi PR template (Safety story / Product Description / Technical Summary / QA Plan). Also triggers on "ship this" or when implementation is complete and ready to push. For repos without these conventions, use the generic `create-pr` skill instead.

Fix CI failures and address review feedback on the current branch's PR. Use when CI is failing, review comments need addressing, or you need to push fixes for an open PR. Supports --dry-run to preview without changes.

Run a full dependency audit for a project — covers Python (pip-tools) and front-end (npm/yarn) if present. Produces report, applies safe bumps, emits Jira-ready ticket list for risky/EoL items. Use when running quarterly maintenance or on demand.

End of day wrap-up — captures what got done, what didn't, and plans for tomorrow. Weekly close-out on configurable review day (default Friday).

Conversational skill for reviewing, updating, and refining your professional goals.

Morning check-in — surfaces goals, summarizes where you left off, captures today's plan, and gives goal-alignment feedback. Weekly review mode on configurable review day (default Friday).

Prep for 1:1s with your manager — auto-summarizes journal entries since your last sync into a briefing with wins, progress, and blockers.

Use when squashing fixup commits into earlier commits, cleaning up a feature branch with interactive rebase, recovering a dropped or failed autosquash, inserting a reformatting commit before code changes, moving file changes between commits, splitting one working-tree edit across several historical commits, or diagnosing autosquash conflicts.

Use when capturing, reviewing, or resolving open questions and to-dos. Triggered automatically throughout sessions when questions surface in conversation or code, before committing or pushing changes, and when answers are provided by team members.

Use when recording activity in the project log — after design decisions, alternatives considered, conflicts found, open questions added or resolved, or significant document changes.

Use at the start of every session to sync with the latest repo state, surface changes from other developers and agents, and orient before doing any work.

Autonomous (headless/CI) variant of extract-adrs. Extracts ADRs from a single source doc with no human interaction, opens a PR, and never merges. Invoked in GitHub Actions as `/extract-adrs-ci <source-doc-path>`. Do NOT use this interactively — use `/extract-adrs` instead.

Extract Architecture Decision Records from a stable design or spec document. Use when a design doc is finished and its decisions should be crystallised into citable ADRs at docs/adr/. Refuses to run on docs with `status: active` frontmatter. Pass the source doc path as the argument.

Use when preparing a test plan for a software release. Triggered by phrases like "create test plan for X release", "generate test cases for these changes", "what should we test for version X", or when given a milestone, version number, or Jira release ticket.

Spawn and manage Claude Code sessions via ACP — covers full lifecycle (spawn, steer, cancel, resume), mode selection, workspace isolation with git worktrees, and task prompt guidance.

Generate CommCare test YAML fixtures for the cc test run command. Use when the user wants to create a new test, write a test fixture, build a test from a bug report or acceptance criteria, or asks about the test YAML format.