connect-tech

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

Skills (12)

• connect-web-release-notes

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

• docs-affected-by-branch

  Use when working on a CommCare Connect branch, before or after its PR is opened, and the user asks which Confluence docs the change affects or makes out of date, or what belongs in the PR's Documentation section. - mcp__*__executeWrite - mcp__*__executeDestructive - mcp__*__createJiraIssue - mcp__*_

• docs-vs-code-review

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

• groom-sprint-tickets

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

• investigate-user

  Use when a support ticket or a teammate asks what happened to one PersonalID or Connect user on the CommCare app - "look into this user", "investigate <username>", "what did this device do", "why can't this user get an OTP", "is anything odd about this account". Takes a PersonalID username or a Comm

• jira-bug-ticket

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

• jira-feature-request

  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

• jira-spec-doc

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

• jira-tickets-from-plan

  Use when creating Jira tickets from a AI plan.

• post-hoc-points

  Use when the user types /post-hoc-points or asks to point their finished tickets - "post-hoc points", "what did that ticket really take", "points for my done tickets", "which tickets need points". Finds their Jira tickets that were resolved lately and have no post-hoc comment yet, suggests the story

• release-notes

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

• tech-spec

  Use when a technical spec, design doc, or PRD needs creating, reviewing, auditing, condensing, or restructuring — the user supplies a spec file path, PR link, Jira ticket, or pasted spec text and asks whether it is complete, whether it covers everything, to tighten or cut it down, to check it agains

Subagents (1)

• code-simplifier

  Simplifies and refines recently modified Django code (Python, templates, front-end JS) for clarity, consistency and maintainability while preserving all behaviour. Use after writing or changing code; focuses on the current diff unless told otherwise.