Critically evaluate PR review comments, then act on them. Commit fixes for the valid ones, reply to every thread, and resolve it. Be skeptical, because the reviewer (usually another LLM or a bot such as CodeRabbit) lacks project context, history, and intent.…
Add detailed comments to recent code changes explaining what was fixed, why it's needed, and the rationale. Use after making code changes to document the reasoning inline.
Reset the repo after a PR has merged, ready for the next piece of work. Removes the branch's worktree if it has one, goes back to master, pulls, deletes the merged branch locally and on origin, and runs npm install. Use when the user says their PR is merged…