Code review
You finish a feature. Claude has been the one driving, so it already knows — maybe too well — what the code is supposed to do. You are about to push a PR and you want a second opinion that is not colored by everything that happened in this session. Claude Code has three small features that make the git tail end of the Explore → Plan → Code → Commit workflow dramatically smoother.
Review with a subagent
Before you push a PR, ask Claude to run a subagent reviewer over your changes. The subagent runs in its own context window, so it reads the diff with fresh eyes — without the bias the main agent built up while writing the code.
Two configuration rules for a reviewer subagent worth trusting:
Restrict it to read-only tools. A reviewer's job is to flag issues, not to fix them. Read-only tools enforce that boundary so the reviewer cannot silently rewrite what it is supposed to be evaluating.
Check the subagent config into your repo. That way everyone on the team runs the same reviewer with the same standards. Code review becomes a property of the repo, not the individual developer.
The /commit-push-pr skill
The /commit-push-pr skill collapses the entire commit-to-PR flow into a single step. Instead of running git add, writing a commit message, pushing the branch, and opening a PR by hand, you run the skill and Claude handles all of it.
If you have a Slack MCP server configured with channels listed in your CLAUDE.md, the skill will also auto-post the PR link into your team's channel — so review requests land where your team actually lives.
Session linking with --from-pr
When Claude opens a PR via gh pr create, the session is automatically linked to that PR. That link matters later: when you come back two days later to address review comments or fix a failing build, you do not want to reconstruct the session from memory.
Resume the linked session with:
claude --from-pr <PR_NUMBER>
This picks up exactly where you left off — the plan, the exploration, the decisions — so the next pass has the same context the first pass did.
Recap
Three features, three friction points removed. A subagent reviewer gives you a fresh pair of eyes on your own diff. /commit-push-pr collapses commit, push, and PR creation into one step and plugs into Slack if you want it to. --from-pr lets you resume a session against any PR by number. None of them are revolutionary on their own — together they remove the small daily taxes that make git workflows feel tedious.
Key Takeaways
- 1Run a subagent reviewer before pushing a PR — a fresh context window catches what the main agent is biased not to see.
- 2Restrict reviewer subagents to read-only tools and check their configuration into the repo so the whole team reviews against the same rules.
- 3The /commit-push-pr skill handles commit, push, and PR creation in one step, with optional Slack posting via MCP.
- 4Claude Code links the session to any PR it creates; run `claude --from-pr <PR_NUMBER>` to resume work on review comments or failing builds.
- 5These features integrate Claude Code into the git workflow, collapsing the Commit phase of Explore → Plan → Code → Commit into a few keystrokes.