dimagi-claude-workflows

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 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.

Use when creating Jira tickets from a AI plan.

Use when drafting a commit message, naming a branch, writing a PR title, or composing/editing a PR description in any Dimagi repo. Also use before running `gh pr edit --body` against an existing PR.

Use when the user interacts with Jira tickets, epics, or Confluence design docs for the USS team. Triggers when the user mentions a USH ticket key or URL, asks about sprint status, requests ticket summaries or comments, wants to create or find a design doc, or asks to transition a ticket's status.

Generates Markdown release notes for the latest commcare-connect release and posts them to Confluence and Slack. Use when the user asks for Connect release notes, a changelog, or what changed in the last release (no repo URL needed).

Reviews Confluence docs against source code to find inaccuracies and suggest fixes. Use when the user provides a Confluence URL and asks to review, audit, or check if docs are accurate or up to date (GitHub repo not required — inferred from the Confluence space).

Create a Jira bug ticket. Use when the user asks to file, log, report, or create a bug or defect in Jira ("create a bug ticket", "log a bug", "report a bug", "open a ticket for this bug").

Generates a product spec doc in Markdown from a Jira ticket. Use when the user provides a Jira ticket ID (e.g. CCC-284) or URL and asks for a spec, design doc, or tech spec ("write a spec for this ticket", "make a spec from this Jira").

Generates Markdown release notes for the most recent release of a GitHub repository. Use when the user asks to "generate release notes", "write a changelog", or "summarize the last release" for a GitHub repo (owner/repo or full URL).

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

Slash command: /groom-sprint-tickets <sprint name>. Do NOT auto-invoke. Only runs when explicitly called via slash command.

Use when the user wants to divide up, assign, or distribute unscored Jira tickets from the SAAS deet week board (board 252) for scoring/grooming. Triggers on phrases like "score deet week", "split up the unscored tickets", "divide unscored tickets", "assign tickets for scoring", or "who should score these". Mobile tickets always go to Ahmad; the rest get split evenly among the other Platform devs. Posts the result to Slack

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

Prepare for the next sprint. Reviews your board and drafts your sprint plan message.

Create Jira feature request tickets (Stories) in the CI project using Dimagi's form 134 format. Use this skill whenever a user wants to submit, log, or create a feature request, new feature idea, product enhancement, or user story in Jira. Triggers on phrases like "create a feature request", "submit a feature idea", "log a feature", "I want to request a feature", "add this to the backlog", "create a story", or any time someone describes something they want the product to do that it doesn't do yet. Always use this skill when feature requests or product enhancements need to be tracked, even if the user doesn't say "Jira" or "ticket" explicitly.

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".

Upgrade a Python or JS dependency safely. Given a library name, finds the latest safe version, reviews the changelog, assesses impact based on how the library is used in the repo, performs the upgrade, and creates a PR with the changelog and assessment. Use this whenever someone asks to upgrade, bump, or update a package/library/dependency.

Create a security ticket in JIRA for a CVE from a GitHub Dependabot alert URL.

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

Create a SAAS Jira ticket. Just describe what you're working on and it handles the rest.

This skill should be used when the user asks to review code, check a PR, audit a file or module, look at code quality, assess a codebase, or says things like "what do you think of this code", "review my changes", "look at this file", "check this PR", or "does this look right". Trigger on any request to evaluate, critique, or assess code — even casually phrased ones. Performs thorough, senior-engineer-quality code reviews that go beyond bug detection.