git

Git Integration Command

You are managing git workflow in alignment with the task-based development process.

Input

• Action: {{1}}

  • branch - Create a branch for a task
  • commit - Commit changes for current task
  • finish - Complete task branch (commit, optionally merge)
  • status - Show git status relative to tasks
  • sync - Sync task branches with main/develop

• Task Number: {{2}} (optional, defaults to current in-progress task)

Prerequisites

Verify git is initialized:

git rev-parse --is-inside-work-tree

If not a git repository, ask if user wants to initialize one.

Actions

branch - Create Task Branch

Create a new branch for working on a specific task.

Process:

1. Identify the task (from argument or first progress task)
2. Read task file to get title
3. Generate branch name: task/XX-task-slug
   • Example: task/05-lexer-tokenizer
4. Check if branch already exists
5. Create and checkout the branch:

   git checkout -b task/XX-task-slug
   

6. Confirm to user:

   "Created and switched to branch task/05-lexer-tokenizer Ready to work on Task 05: Lexer/Tokenizer"

Branch Naming Convention:

• Prefix: task/
• Task number: Zero-padded (01, 02, etc.)
• Slug: Lowercase, hyphenated task title
• Example: task/07-stream-reader-base

commit - Commit Task Progress

Create a comprehensive commit for the current task work.

Process:

1. Check for uncommitted changes
2. Identify current task (from branch name or in-progress task)
3. Analyze changed files and diffs to understand what was modified
4. Stage all changes (or ask user what to stage)
5. Auto-generate comprehensive commit message:
   • Descriptive title (max 50 characters)
   • Detailed description (3-4 lines max) based on actual code changes
   • NEVER add acceptance criteria in message body
   • NEVER add author information in message body
   • NEVER add generated with/by in message body
6. Show generated commit message to user for approval
7. Create the commit after user approval
8. Confirm to user