Investigate a technical spike by gathering requirements interactively, analyzing the codebase with grep and read tools, researching libraries and technologies, evaluating options, and producing a structured report with a high-level proposals doc (for managers/PMs/designers) and detailed technical analysis. Uses Monte Carlo simulation for timeline forecasting with confidence levels. Optionally integrates with JIRA if a ticket ID is referenced.
Investigate a bug using the 5 Whys root cause analysis technique. Fetches ticket details from JIRA (if a ticket ID is provided), checks for previous investigation reports, defines Fix Verification Criteria before digging in, traces the bug across frontend and backend repos, and generates a structured investigation report with timeline and recommendations. Requires jira CLI if using a ticket ID.
Investigate and plan implementation of a new feature using Acceptance Criteria as the central organizing principle. Fetches ticket details from JIRA, validates and clarifies AC before any planning begins, maps every implementation task back to a specific AC, and generates an implementation plan, technical design, task breakdown, and PR checklist template. Requires jira CLI.
Explain what work is needed for a JIRA ticket in plain language. Fetches ticket details from JIRA, searches GitHub for related PRs and commits, identifies affected code areas, and produces a plain-English breakdown with acceptance criteria, task checklist, and suggested first steps. Requires jira and gh CLIs. Usage: /skill:ticket-explainer PROJ-1234
Fetch all review comments from a GitHub PR, categorize them by priority, present an implementation plan for user approval, then systematically implement each approved change. Does not commit or push — all git actions remain manual. Requires gh CLI. Usage: /skill:implement-pr-feedback <PR URL or number>
Fetch and review a GitHub pull request with comprehensive analysis — pattern consistency against existing codebase, junior-friendly explanations, documentation links, manual testing steps with edge cases, and Fix Verification Criteria. Requires gh CLI. Usage: /skill:pr-review <PR URL or number>
Generate a JIRA-linked conventional commit message from staged git changes. Extracts ticket number from branch name (PRO-####, BUG-###), checks for new TODO comments, formats the message, and copies it to clipboard via pbcopy. Does not commit — output only.
Generate a Deckset-formatted markdown presentation about the current repository, the current git branch's changes, or a custom topic. Asks the user to choose scope, gathers information from the codebase or branch diff, and writes a .md file to ~/slidedecks/<project-name>/. No external tools required.