dev
claudeThink a feature through with /dev:design, then plan, build, verify and land code changes through one pipeline — /dev:fix, /dev:task, /dev:feature, /dev:build and /dev:deliver — with approval gates, sequential implementers, a subtractive prune pass and stacked PRs. On request, /dev:review fixes what nobody would argue with and posts the rest that survived a refutation pass as inline PR findings, /dev:fix-pr-comments acts on the unresolved PR threads and asks in chat where a fix needs a choice, /dev:review-and-fix loops the two until review calls the branch finished, /dev:explain-pr explains a PR or a whole stacked chain in plain language, and /dev:update-packages updates every dependency in verified batches and flags the deprecated or abandoned ones. Project-specific checks and git flow come from the project's own verify and git-workflow skills, which /dev:setup and /git:setup write
14 skills