A Collection of 5 Posts

Posts

1. The useful version of issue-to-PR automation is not "let the agent merge code." It is "give the agent a well-scoped issue, let it open a draft pull request, and keep the existing GitHub quality gates in charge."

2. An agent saying "done" is not the same as a change being shippable. Claude Code hooks give you a deterministic layer around the agent loop: run checks after edits, and block final completion when the repository is not green. This article shows a practical pattern using PostToolUse and

3. Git worktrees make it easy to run several coding agents in parallel. They do not make the resulting branches compatible. If three agents edit the same files, the merge queue becomes the first place you discover the collision. A lightweight "clash predictor" can catch overlapping edits earlier by

4. OpenCode permissions are useful when you are driving agents from a terminal. They become awkward when the human approver is not sitting at that terminal. A better shape for remote approval is event-driven: subscribe to permission.asked, send the request to a mobile queue, then handle permission.replied as the

5. Repo-wide search is one of the easiest ways to ruin an agent session. The main thread reads dozens of files, follows dead ends, and keeps all that intermediate context around while trying to implement a focused change. Claude Code subagents are a useful escape hatch. They run in isolated context,