skills.rest
oto1720
oto1720COMMUNITY
Explore all skills by this author →
GitHub

dev-flow

Automate the end-to-end Dev Flow from issue to PR review.

1|Updated Feb 23, 2026
Search Tags:#automation#workflow#github#issue#ci-cd#pull-request#dev-flow
One-click install
npx skills add https://github.com/oto1720/claude-agents-skills --skill dev-flow-oto1720
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-flow
Source: https://github.com/oto1720/claude-agents-skills/tree/main/skills/dev-flow
Command: npx skills add https://github.com/oto1720/claude-agents-skills --skill dev-flow-oto1720

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines a GitHub issue through the full development lifecycle—planning, implementation, commits, PR creation, and review—reducing manual handoffs and context switching.

Core Features & Use Cases

  • End-to-end automation: From issue to PR, including planning, branching, and reviews.
  • Project documentation integration: Reads CLAUDE.md and project docs to align implementation with standards.
  • Error handling & reporting: Detects common failure modes and provides actionable guidance to recover.

Quick Start

Provide an issue number to trigger the full Dev Flow from planning to PR review.

Frequently Asked Questions about dev-flow

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

FAQPage Schema
How do I automate the workflow from a GitHub issue to a pull request?▼

Automating the workflow from a GitHub issue to a pull request is done by reading project documentation, generating an implementation plan, creating a feature branch, implementing changes, and opening a PR for review. Provide an issue number to trigger the full Dev Flow.

What is the best way to automate CI-CD and pull request generation from issues?▼

The best way to automate CI-CD and pull request generation from issues is using an end-to-end Dev Flow that handles planning, branching, commits, and PR creation, reducing manual handoffs and context switching throughout the development lifecycle.

Do I need project documentation to automate issue implementation and PR creation?▼

Yes, you need project documentation to automate issue implementation. The Dev Flow reads CLAUDE.md and project docs to align implementation with your project standards, ensuring the automated changes meet your repository's guidelines before opening a PR.

How does error handling work when automated issue to PR workflow fails?▼

Error handling when automated issue to PR workflow fails involves detecting common failure modes and reporting them with actionable guidance to recover. This ensures you receive specific instructions on how to resolve edge cases instead of generic failure messages.

Can I use automated dev flow to handle edge cases during code implementation?▼

Yes, you can use automated dev flow to handle edge cases during code implementation. The workflow detects common failure modes during the transition from issue to PR review and reports failures with actionable guidance to help you recover.

Related Skills

Explore More Software Engineering Skills→
ZoimbackZoimback

github-copilot-instructions

Create and edit the .github/copilot-instructions.md file for repository-wide GitHub Copilot standards.

Community
Basic
jon23djon23d
3

pipeline-watch

Monitor CI/CD pipeline check statuses for pull requests on GitHub and Gitea.

Community
Intermediate
L-LesterYuL-LesterYu
51

github

Manage GitHub repositories, issues, pull requests, and CI/CD workflows via the GitHub CLI.

Community
Intermediate
zenbuappszenbuapps

git-commit

Generates conventional commit messages and stages relevant changes from diffs.

Official
Advanced