devflow-dev
Scannednpx machina-cli add skill docutray/docutray-claude-code-plugins/devflow-dev --openclawDevFlow: Development Implementation Flow
Implement features based on GitHub issues, creating a development branch, following best practices, and ending with Pull Request generation.
When to Use
Use this flow when you need to:
- Implement a feature from a GitHub issue
- Develop code following structured workflow
- Create a pull request from an issue
- Follow project conventions and best practices
Flow Diagram
flowchart TD
A([BEGIN]) --> B[Download and parse GitHub issue]
B --> C{Uncommitted changes?}
C -->|Yes| D[Ask user: stash/commit/discard]
D --> E
C -->|No| E[Analyze issue specification]
E --> F[Create feature branch]
F --> G[Prepare workspace and dependencies]
G --> H[Run initial validation]
H --> I[Extract task checklist from issue]
I --> J{All tasks complete?}
J -->|No| K[Implement next task]
K --> L[Run tests for changes]
L --> M[Commit with descriptive message]
M --> J
J -->|Yes| N[Run full validation suite]
N --> O{Validation passed?}
O -->|No| P[Fix issues found]
P --> N
O -->|Yes| Q[Generate PR description]
Q --> R[Create Pull Request]
R --> S([END: Next use /flow:devflow-review-pr])
Node Details
1. Download Issue
Fetch complete issue information from GitHub including:
- Title and description
- Acceptance criteria
- Labels and assignees
- Comments and discussion
2. Check Git State
Ensure clean working directory before starting.
3. Create Branch
Create properly named branch:
- Format:
feat/issue-<number>-<slug> - Based on:
mainor epic branch if applicable
4. Prepare Workspace
- Install/update dependencies
- Run initial validation
- Ensure clean starting point
5. Implementation Loop
Process each task from the issue checklist:
- Implement one task at a time
- Run relevant tests
- Make frequent commits
- Validate no regressions
6. Final Validation
Run complete validation suite:
- All tests
- Linting
- Type checking
- Build verification
7. Create PR
Generate comprehensive PR with:
- Link to issue
- Summary of changes
- Testing performed
- Acceptance criteria verification
Parameters
The flow accepts these arguments:
issue#<number>: Required - the issue to implement--branch=<name>: Optional custom branch name--draft: Create PR as draft--auto-tests: Run tests after each change
Example Usage
/flow:devflow-dev issue#123
/flow:devflow-dev issue#456 --draft
/flow:devflow-dev issue#789 --auto-tests
Output
After completion:
- Feature implemented on branch
- All tests passing
- Pull Request created
- Clear next step:
/flow:devflow-review-pr <pr-number>
Source
git clone https://github.com/docutray/docutray-claude-code-plugins/blob/main/.kimi/skills/devflow-dev/SKILL.mdView on GitHub Overview
DevFlow automates implementing features from GitHub issues by guiding you through a complete development workflow: create a branch, implement tasks, validate, and generate a PR that references the issue.
How This Skill Works
The flow fetches the GitHub issue, ensures a clean git state, creates a branch named feat/issue-<number>-<slug>, and iterates through the issue's tasks. After each task, it runs tests and commits with a descriptive message, then performs a full validation before generating a PR description and creating the PR.
When to Use It
- Implement a feature described in a GitHub issue
- Follow a structured, task-based development workflow with incremental validation
- Create a pull request that references the issue and its acceptance criteria
- Align changes with project conventions and best practices
- Ensure a clean working directory before starting the implementation
Quick Start
- Step 1: /flow:devflow-dev issue#123
- Step 2: Implement tasks from the issue and run tests after each change
- Step 3: Generate PR and reference the issue (link + summary)
Best Practices
- Download and parse the issue completely, including acceptance criteria and checklist
- Keep the working directory clean; stash, commit, or discard changes as needed
- Name branches consistently as feat/issue-<number>-<slug> from main or the appropriate epic branch
- Tackle one task at a time, run relevant tests, and commit with descriptive messages
- Run the full validation suite (tests, linting, type checks, build) before PR
Example Use Cases
- Implementing a new feature described in issue #123 with a dedicated feature branch
- Adding a UI component per issue #234 while validating at each step
- Refactoring a module as per issue #345 and running incremental tests
- Exposing a new API endpoint per issue #456 with acceptance criteria linked
- Enhancing documentation and tests per issue #567 aligned to project conventions