Skip to content

Latest commit

 

History

History
56 lines (43 loc) · 1.8 KB

AGENTS.md

File metadata and controls

56 lines (43 loc) · 1.8 KB

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

Ruby Toolchain (rbenv + Bundler)

Use rbenv for all Ruby commands. Derive Ruby version from .ruby-version and Bundler version from Gemfile.lock.

export RBENV_VERSION="$(cat .ruby-version)"
export BUNDLER_VERSION="$(awk '/^BUNDLED WITH$/{getline; gsub(/^[[:space:]]+/, "", $0); print; exit}' Gemfile.lock)"

Run commands through:

rbenv exec bundle "_${BUNDLER_VERSION}_" install
rbenv exec bundle "_${BUNDLER_VERSION}_" exec rspec
rbenv exec bundle "_${BUNDLER_VERSION}_" exec rubocop

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update issue status - Close finished work, update in-progress items
  4. PUSH TO REMOTE - This is MANDATORY: 
    git pull --rebase
bd sync
git push
git status  # MUST show "up to date with origin"
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds