dev-utils

Plugin dev-utils from marketplace dimagi-claude-workflows in dimagi/dimagi-claude-workflows. Commands read from the repo's manifest — 2 days ago.

Skills (14)

• add-mobile-string

  Use when the user asks to add a new Android string resource with translations to the CommCare Android project, given a string resource name and English text

• audit-dependencies

  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.

• babysit-prs

  One sweep over my open PRs — address new review comments, check CI, branch freshness, lint/format & generated-artifact drift, and description sync, fixing and pushing — tracking state so reruns skip already-handled work. Designed to be driven by /loop. Pass a PR number to work a single PR instead.

• create-mobile-pr

  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 Summ

• create-pr

  Use when the user asks to create, open, or submit a GitHub pull request, says "make a PR", "open a PR", or wants to commit, push, and turn the current branch into a PR. For mobile/CommCare repos with JIRA-prefixed tickets and RELEASES.md QA notes, prefer create-mobile-pr instead.

• explain-diff-html

  Use when the user asks for a rich explanation of a code change, diff, branch, or PR. Produces HTML output.

• git-rebase

  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

• grill-me

  Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

• iterate-pr

  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.

• pr-risk

  Use when grading how risky a Dimagi mobile/CommCare pull request is and setting its risk label (Low Risk, Medium Risk, High Risk) — "grade the risk on this PR", "what risk label should this get", "regrade #4012 after my changes", "set the risk label". Called by `create-mobile-pr` before a PR opens;

• pr-status-report

  Use when the user asks for a PR report, PR status, open PRs overview, or wants to know which pull requests need their attention in the current repository

• record-mobile-demo

  Use when the user wants a demo video (or GIF) of a mobile change - "record a demo", "make a video of this change", "demo this for the PR", "screen-record the new flow". Drives a plugged-in Android device or an emulator through the flow, records a clean replay with scrcpy, and polishes it with captio

• step-by-step

  Build an implementation one small unit at a time (usually a function), pausing after each so the user can explain the code back in their own words before anything else is written. Use when the user invokes /step-by-step or asks to go "one function at a time", "slow down so I can follow", or "let me

• vertical-ordering

  Use when writing new functions, extracting helpers, refactoring modules, or reorganizing code — any time function placement order is a decision

Slash commands (2)

• /dev-utils:pr-walkthrough

  Generate a comprehensive reading guide for a pull request — includes a narrative reading order, architecture impact analysis, review comment summary, prior state context, and potential concerns ranked by risk.

• /dev-utils:review-plan

  Interactively review a plan across architecture, code quality, tests, and performance before any code changes.

Similar plugins