Creates git branches and GitHub pull requests following the project naming convention. Enforces the format type-issuenumber-short-description for both branches and PR titles. Use when creating a branch, opening a PR, or asking about branch/PR naming.
Implements a GitHub issue end-to-end. Reads the issue, creates a branch and PR, breaks work into tasks saved to plans/, executes tasks in parallel via sub-agents, and commits after each task. Use when the user says /implement, asks to work on an issue, or references an issue number to start implementing.
Decomposes features or releases into BDD-formatted GitHub issues with Given/When/Then scenarios and test cases. Creates milestones, assigns labels, and adds issues to the project board. Use when starting a new release, planning a feature, or creating issue tickets.
Reviews a GitHub PR using three parallel sub-agents (software engineer, data engineer, QA engineer), synthesizes their findings, and posts a structured review comment. Use when reviewing a PR, when the user says /review-pr, or when asked to review code changes.
Provides verified DuckPGQ query patterns for the sqlprismgraph property graph. Triggers when writing SQL/PGQ MATCH queries, implementing graph tools (#31-36), calling pagerank/wcc/lcc functions, or debugging DuckPGQ syntax errors like "RETURN" or unbounded path errors.