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:

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

Investigation First

<investigation_rules> Before writing any code:

• Read every file referenced in plan.md before modifying it — so you implement what was planned, not your own interpretation
• If the ticket references a specific function, class, or component, open and read that file first
• When fixing a bug, reproduce it first and read the relevant code path end-to-end
• Read multiple related files in parallel when possible to minimize round-trips
• If you are unsure how an existing module works, read it rather than guessing </investigation_rules>