repo-practicing-trunk-based-developmentlisted

# Trunk Based Development Skill ## Purpose This Skill provides comprehensive guidance on **Trunk Based Development (TBD)** - the git workflow used throughout this repository where all development happens on the `main` branch with small, frequent commits. **When to use this Skill:** - Planning git workflow for new features - Deciding whether to create a branch - Understanding when branches are justified - Managing incomplete work using feature flags - Navigating environment branches (deployment only) - Creating plans with git workflow specifications - Implementing AI agent default behaviors ## Core Concepts ### What is Trunk Based Development? **Trunk Based Development (TBD)** is a git workflow where: - **All development happens on `main` branch** (the "trunk") - **Small, frequent commits** pushed directly to `main` - **Minimal branching** - branches are exceptional, not standard - **Short-lived feature branches** (if used) - < 1 day, merge quickly - **Feature flags** for incomplete work (not branches) - **Continuous integration** enabled by frequent merges ### Why TBD? **Benefits**: - **Reduced merge conflicts**: Small commits integrate continuously - **Faster feedback**: Changes visible immediately - **Simpler workflow**: No complex branching strategies - **Better collaboration**: Everyone works on latest code - **Easier rollback**: Small commits easier to revert than large branches **Tradeoffs**: - **Requires discipline**: Commits must be small and safe - **Nee