bender

Summarize the most recent commit or pending changes — what they do, how they fit into the existing code, and a diagram if the change is structural.

Orchestrates the full roadmap-to-committed-code flow. Iterates through milestones — implementing, testing, reviewing, and committing each — with human approval gates.

Use at the start of a session when there is a roadmap or milestone document and you want to pick up the next item. Orients from a cold start, locates the roadmap, identifies the next unfinished item, and proceeds to implementation.

Use when you have a large feature, project, or initiative to plan. Breaks it into discrete, sequenced milestones and writes them to a ROADMAP.md that milestone can consume.

Use before claiming any work is complete, fixed, or passing. Use before every "done", "fixed", "tests pass", or "it's working" statement.

Generate a GitHub pull request description from the current branch. Produces a high-level, markdown-formatted summary and copies it to the clipboard. Pass a base branch if it's not main/master.

Use when starting any new feature, significant change, or architectural decision. Explores requirements and options before any implementation begins.

Use when you want an independent review of code before committing or merging. No argument reviews all uncommitted changes. Pass "branch" to review everything on the current branch vs. main. Pass a file path or git ref for a targeted review.

Use when implementing any new feature, fixing a bug, or refactoring existing code. Enforces red-green-refactor discipline throughout.

Use when encountering any bug, test failure, unexpected behavior, or when a previous fix attempt did not work. Use before proposing any solution.