connect-tech

Reviews Confluence documentation against actual source code AND internal documentation standards to find inaccuracies and gaps, then suggests specific fixes. Use this skill whenever a user shares a Confluence page URL and asks to "review the docs", "audit documentation", "compare docs to code", "check if the docs are accurate", "update docs to match the code", or "what's wrong with this documentation". Also trigger when a user says things like "the docs might be out of date", "sync the docs with the code", or "check our docs against the guidelines". The skill fetches the Confluence page and ALL child pages, clones and reads relevant code, and produces a concise prioritized list of specific doc changes needed — only things that need fixing, no confirmation of what's already correct. Always use this skill when the user provides a Confluence URL — a GitHub repo URL is NOT required, the skill infers the correct repos automatically.

Create Jira bug tickets with all required and optional fields. Use this skill whenever a user wants to file, log, report, or create a bug, defect, or issue in Jira. Triggers on phrases like "create a bug ticket", "log a bug", "file a Jira issue", "report a bug", "open a ticket for this bug", or any time someone describes a software problem and wants it tracked. Always use this skill when bug reporting or Jira ticket creation is involved, even if the user doesn't say "skill" or "Jira" explicitly.

Generates a full product spec doc in Markdown from a Jira ticket ID or URL. Use this skill whenever the user shares a Jira ticket ID (like CCC-284) or a Jira URL (like https://dimagi.atlassian.net/browse/CCC-284) and asks for a spec doc, design doc, tech spec, or product specification to be created or drafted from it. Also trigger when the user says things like "write a spec for this ticket", "generate a spec from this Jira", "turn this ticket into a spec", or "make a spec doc for [ticket ID]". The skill fetches the ticket's title, description, and metadata from Jira, then produces a structured Markdown file with both a Design Doc section and a Tech Spec section following the Connect Spec Doc template format. Always use this skill when a Jira ticket is the primary input and a spec doc is the desired output.

Generates Markdown release notes for the most recent release of a GitHub repository. Given a GitHub repo URL (or owner/repo), this skill finds the latest two releases, collects all PRs merged between them, categorizes each change as New / Improvement / Fix / Infra / Docs, and produces a clean, grouped Markdown file saved to the outputs folder. Use this skill whenever the user asks to "generate release notes", "write a changelog", "summarize what changed in the last release", "what was in the last release", or similar. Also trigger when the user provides a GitHub repo URL or owner/repo string alongside any mention of releases, PRs, or changelogs. The skill works for any public or private GitHub repo accessible via the user's `gh` CLI session.