build-ticket

Bobby Build Skill

This skill handles implementation using TDD methodology. Commits code to the current branch.

Before Starting

1. Check learnings — Read .claude/skills/bobby-build/learnings.md + .claude/skills/bobby-build/learnings.local.md
2. Health check — Verify dev environment:

Worktree Isolation (Recommended for Concurrent Sessions)

If multiple bobby sessions may run at once, work inside a per-ticket git worktree so concurrent sessions can't flip each other's branches mid-build.

1. Check if the ticket already has a worktree: read the ticket frontmatter for worktree_path
2. If not, create one: bobby worktree create {ID}
3. cd into it: cd "$(bobby worktree path {ID})"
4. All subsequent git/test/build commands run inside that worktree

The worktree is on its own branch (bobby/tkt-{id}-ticket by default) branched off origin/main. Other sessions in the main checkout or other worktrees cannot affect it.

If you skip worktree isolation, fall through to Branch Guard below.

Branch Guard

Before writing any code, check your branch — commits to main bypass review and can break CI:

1. Run git branch --show-current
2. If on main or master: create a feature branch first:
   • git checkout -b tkt-{ID} (e.g., tkt-042-add-login)
   • Use the ticket ID and a short slug from the ticket title
3. If already on a feature branch: continue on the current branch

NEVER commit directly to main/master.

Safety Rules

<safety_rules>

• Never run destructive commands: rm -rf, DROP TABLE, git push --force, git reset --hard, git clean -fd
• Only modify files related to this ticket. Check git diff --stat before committing.
• Do not edit .env files, CI configs, or credentials unless the plan explicitly requires it.
• Do not install global packages or modify system-level configuration. </safety_rules>

Picking Up Work

1. Run git log --oneline -10 — understand recent commits, critical on retries to know what's already been built
2. Read the ticket's ticket.md, plan.md, and test-cases.md in parallel
3. Check for rejection comments — if this is a retry, read the rejection feedback first