dev-workflow

Coordinate Git operations with ticket management across development workflows.

Updated Feb 4, 2026

Search Tags:#automation #git #workflow #development #branching #conventional-commits #ticket-tracker

Ready to run

npx skills add https://github.com/cbown75/ai --skill dev-workflow-cbown75

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-workflow
Source: https://github.com/cbown75/ai/tree/main/.claude/skills/dev-workflow
Command: npx skills add https://github.com/cbown75/ai --skill dev-workflow-cbown75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines end-to-end development workflows by coordinating Git operations with ticket management to ensure consistent collaboration and traceability.

Core Features & Use Cases

Orchestrates the interplay between git-conventions and ticket-tracker to provide a unified workflow for starting work, creating branches, committing, and creating PRs.
Enforces conventional commits, standardized branch names, and automatic ticket transitions to reduce manual overhead and misalignment.
Use Case: A developer wants to start work on a feature by creating a ticket, a feature branch, and an initial PR while keeping the ticket status in sync.

Quick Start

Start the dev-workflow to begin a new development task by loading the required child skills and generating a ticket plus a branch.

Frequently Asked Questions about dev-workflow

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

FAQPage Schema

How do I automate Git branch naming and ticket status transitions together?▼

Automating Git branch naming and ticket status transitions requires coordinating Git operations with ticket management. This workflow loads child skills to generate standardized branch formats, conventional commit messages, and automatic ticket updates across your development cycle.

What is conventional commit workflow automation for development teams?▼

Conventional commit workflow automation enforces standardized commit messages, branch naming formats, and ticket synchronization to reduce manual overhead. It orchestrates the interplay between Git conventions and ticket tracking for consistent collaboration and traceability.

How do I create a feature branch and sync a ticket status at the same time?▼

Creating a feature branch and syncing a ticket status simultaneously involves starting a unified development workflow. The system handles epic discovery, generates a standardized branch name, and transitions the ticket status automatically across connected tracking tools.

Do I need separate git-conventions and ticket-tracker skills to automate my workflow?▼

Yes, git-conventions and ticket-tracker skills are required child dependencies for this workflow. The orchestrator loads these components before operations to provide standardized branch formats, conventional commit messages, and automated ticket updates.

Can I use this automated workflow for submitting pull requests and updating tickets?▼

Yes, this workflow handles end-to-end development tasks including submitting pull requests and updating ticket statuses. It coordinates Git operations with ticket management to ensure consistent collaboration and traceability throughout the entire process.

What's the best way to standardize branching and commits across a development team?▼

Standardizing branching and commits across a team is best achieved by enforcing conventional commit messages and standardized branch naming formats. This workflow orchestrates these conventions automatically while keeping ticket statuses in sync to reduce misalignment.