tbdflow

Automate trunk-based Git workflows with the tbdflow CLI.

61|5|Updated Jul 6, 2025
One-click install
npx skills add https://github.com/cladam/tbdflow --skill tbdflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tbdflow
Source: https://github.com/cladam/tbdflow/tree/main
Command: npx skills add https://github.com/cladam/tbdflow --skill tbdflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The tbdflow skill provides a robust means to automate and enforce trunk-based development workflows using the tbdflow CLI. It is designed to reduce decision fatigue by ensuring branches are short-lived, commits are standardised, and trunk integrity is preserved.

Core Features & Use Cases

  • Enforce short-lived branches to accelerate integration and maintain a clean history.
  • Standardise commit messages with Conventional Commit lint rules and optional DoD checks.
  • Sync with trunk, merge completed work back to main, and generate release notes across monorepos when applicable.

Quick Start

Start by syncing with trunk, then create a short-lived branch, commit changes, and finally complete to merge back to main.

Frequently Asked Questions about tbdflow

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

FAQPage Schema
How do I enforce trunk-based development workflows in Git?

Trunk-based development workflows are enforced by automating short-lived branch creation, commit linting, and trunk syncing to preserve main branch integrity. This reduces decision fatigue and maintains a clean, standardized commit history.

How do I standardize commit messages with conventional commits and DoD checks?

Conventional commits are standardized by applying lint rules and optional Definition of Done checks during the commit process. This ensures commit messages follow strict formatting guidelines before changes are merged back to the main branch.

What is the best way to manage short-lived branches and merge them back to main?

Short-lived branches are managed by creating them from a synced trunk, committing changes, and merging them back to main upon completion. This approach accelerates integration and maintains a clean history across monorepos.

Can I generate release notes across monorepos after merging to the main branch?

Release notes can be generated across monorepos when merging completed work back to main. This functionality is integrated into the trunk-based workflow to document changes and maintain release history.

Do I need a specific CLI to automate Git workflow actions and branch validation?

A specific CLI is required as the sole interface for Git workflow actions, branch validation, and DoD checks. It automates the entire process from starting work on tasks to generating release notes.

Why use trunk-based development instead of other branching strategies for continuous integration?

Trunk-based development accelerates continuous integration by enforcing short-lived branches and frequent trunk syncing. This approach reduces merge conflicts and decision fatigue compared to long-lived feature branches.