dev-flow

Orchestrates the task-to-PR workflow with OpenSpec scaffolding, branch validation, and CI monitoring.

2|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/Wizarck/nexandro --skill dev-flow-wizarck
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-flow
Source: https://github.com/Wizarck/nexandro/tree/main/skills/dev-flow
Command: npx skills add https://github.com/Wizarck/nexandro --skill dev-flow-wizarck

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting a non-trivial code change normally requires re-reading multiple specs to remember the correct branch naming, OpenSpec change scaffolding, worktree setup, pre-flight checks, and PR conventions. This Skill automates the canonical task-to-PR-to-release flow so developers follow the playbook consistently without manual bookkeeping. ## Core Features & Use Cases - Change Scaffolding (start mode): Derives a change-id from a description, scaffolds an OpenSpec change (proposal.md, tasks.md, specs), creates a conventional branch, optionally provisions a git worktree, and installs an auto-tick prepare-commit-msg hook. - Shipping Automation (ship mode): Validates branch naming and OpenSpec change existence, runs pre-commit, pytest, and ruff checks, verifies tasks.md completeness, pushes the branch, opens a PR with an auto-generated body, and watches CI. - Use Case: A developer wants to add retry-with-backoff to a notification queue. They run the start command to scaffold the change and branch, implement with conventional commits that auto-tick tasks.md boxes, then run the ship command to validate, push, and open a monitored PR. ## Quick Start Ask the AI to run /dev-flow start with a short description of your change, then run /dev-flow ship when implementation is complete to open the PR.

Frequently Asked Questions about dev-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate branch creation and PR opening for a new feature?▼

Use the start mode with a change description to scaffold an OpenSpec change, create a conventional branch like feat/my-change, and install the auto-tick git hook. When implementation is done, run ship mode to validate, push, and open the PR with gh pr create.

What is the difference between dev-flow start and dev-flow ship?▼

Start scaffolds the OpenSpec change, branch, optional worktree, and git hook at the beginning of work. Ship runs pre-flight checks (pre-commit, pytest, ruff), verifies tasks.md completeness, pushes the branch, opens the PR, and optionally monitors CI.

When should I bypass this workflow for small changes?▼

Trivial one-line fixes like typos or version bumps should bypass the skill with a regular fix/<short-id> branch and manual PR. The skill is designed for changes that create new files, touch more than 50 lines, or span more than 5 commits.

Does the skill work with AI coding assistants other than Claude Code?▼

Yes, the skill is LLM-agnostic and works with Claude Code, Cursor, Antigravity, Gemini CLI, OpenCode, and human developers. It orchestrates standard git, OpenSpec, and GitHub CLI operations rather than vendor-specific APIs.

Why does ship mode fail with a branch naming error?▼

Ship requires branches matching the pattern <type>/<change-id> such as feat/add-retry-logic. Rename the branch with git branch -m to a valid type prefix (feat, fix, chore, docs, refactor, test, release) before shipping.

What happens if tasks.md has unchecked boxes when shipping?▼

The skill warns with the percentage ticked and asks for confirmation before proceeding. If you continue anyway, the check-tasks-checkboxes workflow will comment on the PR with the gap, so tick boxes honestly or amend tasks.md first.