Code Review - Workflow | GitKraken

Code Review

For devs facing noisy pull requests. Focus on logic changes, build context with AI, and approve with confidence.

Step 1: Start With the Pull Request

Start from the pull request that needs your attention. In Launchpad, find PRs waiting for review and select Review to open them directly in GitKraken Code Review. Before digging into individual lines, establish the scope of the change: what the PR is trying to accomplish, who authored it, which branches are involved, how large the change is, and the conversation surrounding it.

Trigger

• A human or coding agent has opened a pull request that’s ready for review.

Step 2: Focus on What Changed

Move through the changed files using GitKraken Code Review’s diff instead of treating every line as equally important. The Powerful Diff Viewer helps reduce distraction from formatting and mechanical changes, clearly visualizes moved code, and makes meaningful logic changes easier to identify. Mark files as viewed as you work through the PR so you can systematically separate what you’ve reviewed from what still needs attention.

Trigger

• You understand the meaningful changes without getting buried in diff noise.

Step 3: Build Context & Check Readiness

Open the AI Panel when you need help understanding the PR and deciding whether it’s ready to move forward. Use Analysis to summarize the change and surface key insights, Chat to ask follow-up questions about implementation, risk, or intent, and Info to check mergeability, unresolved conflicts, pending reviews, and CI/CD status.

Desired Outcome

• You understand the change, know what needs deeper review, and can see whether anything still blocks the PR from merging.

Step 4: Make the Human Decision

With the changes understood and merge readiness visible, make the review decision yourself. Leave inline or overall comments, request changes when something needs another pass, manage reviewers or assignees, and approve the pull request when you’re confident it’s ready. GitKraken Code Review keeps the review workflow connected to GitHub, so your decision and feedback remain part of the pull request instead of living in a separate AI review system.

Success Criteria

• AI findings and questions have been evaluated by a human.
• Comments or requested changes are captured on the PR.
• The reviewer makes the final approval decision.

Step 5: Get the Tools to Complete this Workflow

You have seen the workflow, now choose the tools that make it repeatable. Kepler keeps agent sessions organized around the task, GitKraken Desktop gives you visual control of branches, commits, pull request prep, and conflicts, and GitLens brings code history and authorship into your IDE. Start with the tool that matches how you work today, or use GitKraken Pro at 60% off to bring the full plan-to-main workflow together under one subscription.

Success criteria

• Download the GitKraken tool that fits where you work most: your agent workspace, repository, or IDE.
• Create a free account and unlock every feature for 14 days.
• Connect your repository and integrations, then put your first agent to work on a task or issue.