skills.rest
liauw-media
liauw-mediaCOMMUNITY
Explore all skills by this author →
GitHub

branch-discipline

Create one Git branch per issue with small, focused commits.

Updated Aug 27, 2026
Search Tags:#git#worktrees#pull-request#commit hygiene#branch discipline#branch-per-issue
One-click install
npx skills add https://github.com/liauw-media/household-expense-tracker --skill branch-discipline-liauw-media
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: branch-discipline
Source: https://github.com/liauw-media/household-expense-tracker/tree/main/.claude/skills/workflow/branch-discipline
Command: npx skills add https://github.com/liauw-media/household-expense-tracker --skill branch-discipline-liauw-media

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforce disciplined Git workflows by guiding users to create one branch per issue with small, focused commits to maintain a clean history.

Core Features & Use Cases

  • One-branch-per-issue: Each branch targets a single issue, feature, or bug fix.
  • Small, logical commits: Commits are atomic and independently revertable.
  • Structured workflow: Use /branch, /branch-status, /branch-done, and mentor interactions to ensure consistency.
  • Worktrees & checklists: Supports git worktrees and per-branch checklists to coordinate parallel work.
  • Use Case: A team seeks predictable PRs and traceable history for audits.

Quick Start

Use the /branch command to create a focused branch for a single issue, then commit with a clear message and run the mentor checklist before PR.

Frequently Asked Questions about branch-discipline

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

FAQPage Schema
How do I enforce a one branch per issue workflow in git?▼

To enforce a one branch per issue workflow, you can use structured commands to create a focused branch for a single issue and apply a checklist-driven process for small, logical commits before opening a pull request.

What is the best way to maintain clean git history with small focused commits?▼

Maintaining clean git history requires keeping commits atomic and independently revertable, which you can achieve through a mentor checklist that ensures commit hygiene and PR readiness across your development team.

How do I use git worktrees to coordinate parallel branch work?▼

Using git worktrees allows you to coordinate parallel work by supporting per-branch checklists, ensuring each scoped issue branch remains isolated and compliant with your team's structured workflow.

Can I use a checklist-driven workflow to ensure pull request readiness?▼

Yes, you can use a checklist-driven workflow with specific commands to verify commit hygiene and branch discipline, ensuring your pull requests are predictable and your history remains traceable for audits.

Does a branch discipline workflow work for teams needing traceable git history?▼

Yes, a branch discipline workflow is designed for software development teams that require clear issue tracking, scoped changes, and consistent commit messages to produce traceable git history for audits.

Related Skills

Explore More Software Engineering Skills→
pegasus-isipegasus-isi

create-issue

Create GitHub issues from templates and initialize linked branches and worktrees.

Official
Advanced
SoSoBurnerSoSoBurner

ship

Automate code deployment by running tests, reviewing diffs, and creating a pull request.

Community
Advanced
trungdo9trungdo9
3

git

Automate commit message validation and manage isolated worktrees for parallel development.

Community
Intermediate
troykellytroykelly
11

clean-commits

Create atomic commits with descriptive messages and pre-commit checks.

Community
Advanced