smart-recipe-planner-ticket-workflow

Enforce git branching, conventional commits, and ticket lifecycle workflows.

2|Updated Oct 14, 2025

Search Tags:#git #release-management #pull-request #conventional-commits #branch-naming #dev-process #ticket-workflow

Ready to run

npx skills add https://github.com/LuisDavidTF/Culina-Smart --skill smart-recipe-planner-ticket-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: smart-recipe-planner-ticket-workflow
Source: https://github.com/LuisDavidTF/Culina-Smart/tree/main/.agent/skills/smart-recipe-planner-ticket-workflow
Command: npx skills add https://github.com/LuisDavidTF/Culina-Smart --skill smart-recipe-planner-ticket-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes ticket-driven development workflows, reducing handoff gaps and drift by enforcing a consistent git branching, commit, and lifecycle process.

Core Features & Use Cases

Standardized Branching: Branches follow a uniform format from dev, such as feat/CSF-123-description, ensuring traceability.
Commit Messaging: Encourages conventional commits aligned with ticket work for clear history and changelogs.
Lifecycle Orchestration: Guides Start Ticket, Finish Ticket, and Release-to-Main steps with explicit commands and PR guidance for reliable delivery.

Quick Start

Ensure you are on the dev branch and up to date.
Create a ticket branch from dev using the type/name convention, e.g., feat/CSF-123-description.
Commit changes using conventional commits, finish the ticket by merging back to dev, and open a PR to main for release.

Frequently Asked Questions about smart-recipe-planner-ticket-workflow

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

FAQPage Schema

How do I standardize git branch naming for ticket-based development workflows?▼

Standardize git branch naming for ticket-based development workflows by adopting a uniform format like feat/CSF-123-description, ensuring traceability from feature work and fixes back to their originating tickets.

What is the best way to manage a git release workflow from dev to main?▼

Manage a git release workflow from dev to main by finishing ticket work, merging changes back to dev, and opening a structured pull request to main for reliable delivery and audit trails across development cycles.

How do conventional commits improve pull request handoffs in a dev process?▼

Conventional commits improve pull request handoffs in a dev process by aligning commit messages with ticket work, providing clear history and changelogs for reliable delivery and audit trails across development cycles.

Do I need to be on the dev branch to start a ticket workflow?▼

Yes, you need to be on the dev branch and up to date to start the ticket workflow, as this ensures a clean baseline before creating a ticket branch using the type/name convention.

Can this ticket workflow process handle both feature development and bug fixes?▼

Yes, this ticket workflow process handles both feature development and bug fixes by targeting software teams managing feature work and fixes through standardized branching, commit messaging, and lifecycle orchestration.

Why does my ticket-based release management process have handoff gaps?▼

Ticket-based release management processes have handoff gaps and drift without a consistent git branching, commit, and lifecycle process, which can be solved by enforcing explicit commands and PR guidance from Start Ticket to Main.