GITKRAKEN Code suggest

Smarter Code Reviews, Instantly

GitKraken Code Suggestions is a review tool that lets teams suggest, edit, and apply code changes inline across any file, not just the diff. Review faster, ship cleaner code, and collaborate on GitHub pull requests directly in GitKraken Desktop, GitLens, and gitkraken.dev.
Start your free trial

What Are GitKraken Code Suggestions?

Inline Edits
Suggest changes directly inside GitHub pull requests.
Suggest changes directly inside GitHub pull requests.
One-Click Apply
Apply reviewer edits instantly in GitKraken.
Apply reviewer edits instantly in GitKraken.
Faster Reviews
Shorten review cycles and merge sooner.
Shorten review cycles and merge sooner.
Higher Quality
Raise code quality with precise edits.
Raise code quality with precise edits.

Why Developers Use Code Suggestions

Faster Team Feedback

Reviewers don’t just comment, they contribute. With suggestions, changes happen inside the code itself, not in a side channel. That means less ambiguity, faster loops, and fewer follow-up questions for the original author.

Fewer Approval Cycles

Skip the usual rounds of “please fix this” comments. Reviewers can suggest exact changes directly in the GitHub PR conversation. Instead of long comment threads, authors see the actual edit and apply it instantly. This keeps the review moving and reduces unnecessary back-and-forth for simple fixes.

Cleaner Pull Requests

Authors can accept or reject suggestions directly in the code suggestion view. Every proposed change is version-controlled and visible to the team, keeping the codebase clean and organized without cluttering PRs with vague comments or unresolved feedback.

Better Remote Collaboration

Distributed teams stay aligned with fewer syncs. Use GitKraken Desktop to create and review suggestions from the same place you manage branches and commits. This supports async reviews, helps distributed teams stay aligned, and makes it easier to give feedback without switching tools.

More Confident Reviews

Suggest changes directly from GitLens in your IDE. It’s easy to fix logic issues or offer cleanups without rewriting the PR. Contributors stay in control while reviewers feel more confident stepping in and making helpful edits across the codebase.

Where You Can Use Code Suggestions

GitKraken Desktop
Review, suggest, and apply without leaving the repo.
GitLens for IDEs
Inline edits and PR reviews built into your IDE.
GitKraken CLI
Suggest and apply changes right in the browser.
Issue Trackers

Interact with code suggestions directly from GitHub.com pull requests.

Start Using Code Suggestions Today

Your team deserves a faster, clearer way to review code.
Start Free GitKraken Pro Trial
Start your free trial
See All Available Plans

Discover More Git Collaboration Features

Explore tools that make every pull request cleaner and every commit smarter.
Automations
AutomationsIncrease consistency across teams
Go To Automations →
Cloud Patches
Cloud PatchesShare early, merge swiftly
Go To Cloud Patches →
Codemaps
CodemapsVisualize your code
Go To Codemaps →
Code Suggest
Code SuggestFaster reviews, fewer restrictions
Go To Code Suggest →
Launchpad
LaunchpadFOne view, zero distractions
Go To Launchpad →
Security Controls
Security ControlsEnsure team security & compliance
Go To Security Controls →
Insights
InsightsBuild smarter, ship faster
Go To Insights →
Merge Tool
Merge ToolMerge conflicts, disarmed
Go To Merge Tools →

Frequently Asked Questions

Code Suggestions let reviewers propose inline changes directly in GitHub pull requests. Instead of only leaving comments, reviewers provide actionable edits that developers apply in one click.

Steps:

  1. Open the GitHub Pull Request in GitKraken Desktop from the Left Panel.
  2. Click “Review to Suggest Changes”.
  3. Make your edits inside GitKraken Desktop and save.
  4. Click Suggest X file change to PR #XX. This will post the suggestion as a GitHub PR comment.


When suggesting a new change, right click into the empty space of the Commit Panel to create a new file.

Example: A reviewer suggests renaming a variable. The developer sees the suggestion come through in a GitHub PR conversation notification and decides whether to approve or reject the suggestion.

In GitKraken Desktop:

Steps:

  1. Open a GitHub Pull Request from the Left Panel or Launchpad.
  2. Locate the inline suggestion.
  3. Click “Apply Suggestion.”
  4. The change is committed automatically.


Example:  Accept a formatting fix instantly without manually editing the file.

No. GitKraken Code Suggestions are available only for GitHub pull requests.

However, anyone with access to the GitHub PR will be able to interact with code suggestions from the PR conversation. Clicking the link will give collaborators the ability to consider the suggestion on the web from gitkraken.dev or open it directly in GitKraken Desktop or GitLens for VS Code.

Suggestions propose actual code edits, while comments are just notes. With suggestions, there is no question what line of code or what file needs editing. This reduces ambiguity and makes changes actionable.

Example: Instead of writing “rename this variable,” you suggest the rename directly.

GitHub Copilot focuses on generating code while you’re writing it. GitKraken Code Suggestions improve code after it’s written, during pull request reviews.

They let reviewers suggest edits across any file, apply them with one click, and speed up team approvals.