dev-workflow

Automate development workflows with task-backed atomic commits and conventional messages.

Updated Aug 27, 2026

Search Tags:#automation #git #workflow #commit #release #task

Ready to run

npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill dev-workflow-ribatshepo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dev-workflow
Source: https://github.com/ribatshepo/cc-auto-orchestrate/tree/main/claude-code/skills/dev-workflow
Command: npx skills add https://github.com/ribatshepo/cc-auto-orchestrate --skill dev-workflow-ribatshepo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development teams waste time and risk with untracked changes and inconsistent release practices. This skill enforces task-backed commits, atomic changes, and a standardized release process to ensure traceability and quality gates.

Core Features & Use Cases

Task-driven commits: Every change must be linked to a tracked task with clear, auditable history.
Conventional messaging: Enforces conventional commit formats and includes task references for easy traceability.
Branch discipline: Prevents commits to main/master and supports a single-branch workflow across subagents.
Release automation: Provides version-bump, tagging, and CI integration for production-ready releases.
Task tooling integration: Works with TaskList, TaskCreate, and TaskUpdate to manage task lifecycles during development.

Quick Start

Verify you have an in-progress task, then begin the workflow by following the task-driven commit and release gates.

Frequently Asked Questions about dev-workflow

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

FAQPage Schema

How do I automate atomic commits and enforce conventional commit formatting in Git?▼

Automating atomic commits requires linking every change to a tracked task and enforcing conventional commit formats. This workflow prevents untracked changes by gating commits with task references, ensuring clear and auditable history traceability.

What is the best way to prevent accidental commits to main while running automated Git workflows?▼

Preventing accidental commits to main requires strict branch discipline within your workflow automation. This approach blocks direct commits to main or master branches, supporting a single-branch workflow across subagents to reduce integration risk.

How do I automate version bumps and release tagging for production-ready deployments?▼

Automating version bumps and release tagging involves integrating standardized release processes with your CI pipeline. This workflow executes version-bump procedures, applies release tags, and enforces quality gates to ensure production-ready automated delivery.

Can I integrate task tracking tools to manage the development lifecycle during automated releases?▼

Integrating task tracking tools allows you to manage the development lifecycle directly during automated releases. This workflow works with TaskList, TaskCreate, and TaskUpdate to link task lifecycles with commit formatting and release gating.

Does automated branch discipline support single-branch workflows across multiple subagents?▼

Automated branch discipline supports single-branch workflows across multiple subagents by enforcing task-backed, atomic changes. This ensures all subagent contributions are traceable and gated, reducing the risk of inconsistent release practices.