In a Bitbucket Cloud pull request, a reviewer types /suggest in a line comment to propose the exact code change, and the author clicks Apply suggestion to commit it to the PR branch without leaving Bitbucket. At initial release, suggestions apply to a single line at a time, with multi-line suggestions slated to be added soon.
Pull request reviews are essential for maintaining code quality, but they can sometimes slow development to a crawl. A common scenario is familiar to many teams: a reviewer spots a minor issue or improvement, leaves a comment describing the change, and then the pull request author must jump back into their development environment to implement the fix. This back-and-forth can introduce delays and disrupt the workflow. At Atlas Bench, we’ve seen how even small inefficiencies in the code review process add up over time. The good news is that Bitbucket Cloud has introduced a better way. In this blog, we’ll explore Bitbucket’s new actionable code suggestions feature and how it can dramatically accelerate your pull request (PR) reviews while keeping your team’s collaboration smooth and productive.
Timely code reviews are crucial for maintaining momentum in a development cycle. When pull requests linger without feedback or approval, they can stall progress and leave features in limbo. Traditionally, even a straightforward suggestion in a PR could create several extra steps for your team:
A reviewer identifies an issue or improvement and writes a comment explaining the suggested change, perhaps even pasting a snippet of code as an example.
The author reads the comment and switches to their code editor or integrated development environment to make the change in the codebase.
After implementing the fix, the author pushes a new commit to the PR branch and notifies the reviewer.
The reviewer then checks the update to verify the change, sometimes repeating the cycle if further tweaks are needed.
Each of these steps may seem minor, but together they contribute to context switching and delays. The reviewer and author both spend time describing and interpreting changes instead of directly improving the code. In a busy team, waiting for someone to apply feedback can mean idle time for others, missed deadlines, or rushed quality control later. Simply put, the old way of handling code suggestions through descriptive comments and manual edits can make the review process longer and more cumbersome than necessary.
Imagine if a reviewer could not only point out an issue but also suggest the exact code change needed, and the author could apply that change with one click. That’s exactly what actionable in-line code suggestions in Bitbucket Cloud bring to the table. This new feature allows reviewers to propose specific code changes within a pull request comment, so the suggested change becomes instantly visible and easy to apply. It transforms code review comments from mere discussion into concrete, ready-to-apply solutions.
In practice, using the feature is straightforward. When reviewing a pull request on Bitbucket Cloud, a reviewer can click the Comment button (usually visible beside the lines of code in the diff view) and start writing a comment as usual. To propose a code change, the reviewer types the special command /suggest in the comment field. This triggers a code suggestion input, allowing the reviewer to write the exact lines of code they recommend inserting or changing. The suggestion appears formatted as an editable diff within the comment, clearly showing the proposed additions or deletions.
Once the comment with the suggestion is posted, the pull request author (or any user with write access to the repository) will see the suggested code change right there in the context of the PR discussion. If the author agrees with the suggestion, they can apply it directly without ever leaving Bitbucket. By clicking Apply suggestion, Bitbucket will automatically insert the change into the codebase on that branch and commit it to the PR. The author even has the opportunity to edit the commit message that accompanies this change, or they can accept a default message provided by Bitbucket. After committing, the pull request is instantly updated with the new changes, and all of this happens without the author opening a separate editor or running a single Git command manually.
This seamless flow is a game changer. Reviewers can be much more precise and helpful in their feedback, essentially contributing code improvements on the spot. Authors, in turn, save time by not having to interpret the feedback or reimplement the solution from scratch the work is already done for them. The entire team benefits from faster review cycles and a more collaborative spirit: code review becomes a shared activity in real time, rather than a slow relay of messages.
Using the actionable code suggestions feature in Bitbucket Cloud is simple. Here’s a quick step-by-step guide to help your team start leveraging this capability in your next review:
Open a pull request for review: Navigate to the pull request in your Bitbucket Cloud repository and go to the Files changed (diff) view or any part of the PR where you can add comments.
Start a comment on a specific line: Find the line of code that you want to suggest changes for. Click the comment icon (a speech bubble) next to that line, which opens a text box for your comment.
Enter a code suggestion: In the comment box, type /suggest on a new line. Bitbucket will recognize this command and provide a special area in the comment to enter your proposed code changes. (Alternatively, you might see a Suggest code button in the editor toolbar clicking that will insert the same command for you.)
Write the proposed code change: After the /suggest command, write the code exactly as you think it should appear. You can add new lines, modify the existing code, or remove lines by leaving them out in your suggestion. This is essentially an inline patch that Bitbucket will display as a mini diff inside your comment.
Post the comment: Submit your comment as usual. The comment will now show your suggested code changes in a formatted block, making it easy for the author and other reviewers to see the difference between the current code and your recommendation.
Apply the suggestion: If you are the pull request author and you agree with the proposed change, simply click the Apply suggestion button shown next to the comment. Bitbucket will prompt you to confirm and allow you to edit the commit message if needed. Confirming this will create a new commit on the PR branch with the suggested changes.
Verify and continue the review: Once applied, the code changes become part of the pull request. The reviewer who made the suggestion can verify that the change was applied correctly by looking at the updated diff. The code review can then proceed, possibly with further suggestions or approvals as needed.
That’s it no separate checkout of the branch, no manual editing in an IDE, and no extra push. The entire process from suggestion to application stays within the Bitbucket UI. It feels almost like a real-time collaboration, where reviewers and authors are co-editing code, yet with all the control and permission checks of a formal pull request process.
The in-line code suggestions feature isn’t just a minor convenience it addresses several pain points in the code review process. Here are some key benefits that Bitbucket’s actionable suggestions bring to development teams:
Faster reviews and merges: By eliminating the need for authors to manually implement straightforward recommendations, pull requests can reach approval and merging faster. A process that might have taken hours or days (waiting for someone to circle back to make a change) can now be resolved in minutes.
Reduced context switching: Reviewers and developers can stay focused within Bitbucket. Reviewers give feedback and propose fixes without juggling multiple tools, and authors apply changes without opening their coding environment. Less context switching means higher productivity and fewer mistakes.
Clearer communication: A suggested code change is unambiguous. Instead of writing a long explanation or risking misunderstanding, the reviewer’s intent is crystal clear. This clarity can prevent miscommunication and further review cycles that occur when a comment isn’t implemented as expected.
Shared ownership of code quality: When reviewers contribute actual code via suggestions, code review becomes a more collaborative effort. The distinction between “my code” and “your feedback” blurs, encouraging a team mindset. Everyone feels invested in writing the best code possible, and junior developers can learn by seeing exactly how a senior engineer would tweak their code.
Less friction for minor fixes: Typos, small logic errors, or formatting issues can be corrected on the spot. Reviewers might have hesitated to point out very trivial issues in the past, to avoid making extra work for the author. Now they can propose a quick fix and move on, keeping the codebase clean without the nitpick becoming a bottleneck.
Audit trail of changes: Each applied suggestion results in a commit on the pull request. This means there is a recorded history of what was suggested and who applied it. In tools like Bitbucket, you can trace that a particular change came from a suggestion by a reviewer. This transparency is great for understanding the evolution of the code and for knowledge sharing during retrospectives or onboarding.
As of the initial release, Bitbucket’s code suggestions feature allows applying changes on a single line at a time. This is fantastic for small tweaks, but what about bigger refactoring that spans multiple lines or an entire code block? Atlassian has anticipated this need. Multi-line suggestions are on the horizon and slated to be added to Bitbucket Cloud’s code review toolkit soon.
With multi-line suggestions, reviewers will be able to select a range of lines (for example, an entire function or a section of a file) and suggest a block of revised code covering that whole section. This enhancement will make the suggestion feature even more powerful, enabling reviewers to propose more substantial changes in one go. Imagine being able to suggest a new 3-line error-handling block or modify an entire loop construct, all within a single comment. That’s the level of convenience we can look forward to.
For teams, multi-line suggestions will mean fewer comments like “On lines 10–15, consider changing X, and on lines 20–22, do Y.” Instead, the reviewer can present the exact revised code across those lines, making it effortless for the author to implement. This will especially help with more complex feedback where multiple lines of code are interrelated.
Bitbucket’s actionable code suggestions can significantly speed up your reviews, but they work best alongside other good habits. Consider these tips to further accelerate your pull request process while maintaining high quality:
Keep pull requests focused and manageable: Smaller, self-contained PRs are quicker to review and test. Even with code suggestions, a massive PR with hundreds of changes is hard to digest. Aim for focused changes so reviewers can respond faster.
Set clear review guidelines and expectations: Establish team norms for how quickly reviews should be completed and how to handle suggestions. For instance, decide when reviewers should directly fix minor issues via suggestions versus when to leave comments for larger design considerations.
Use automated checks for trivial issues: Integrate linters, formatters, and test suites in your CI pipeline so that style issues or obvious errors are caught automatically. This frees reviewers to focus on substance, and any suggestions can concentrate on logic and design rather than syntax.
Communicate openly on the PR: Encourage developers to ask clarifying questions if a suggestion or comment is not understood. It’s faster to discuss and resolve uncertainties in the PR thread than to guess and possibly iterate again. Bitbucket’s interface supports this kind of dialogue well.
Leverage code suggestions for learning: Treat suggested changes as learning opportunities. Reviewers can explain why a suggestion improves the code when necessary, and authors should take a moment to understand the change before blindly applying it. This way, your team continuously improves coding skills and not just the code at hand.
Regularly update and adapt your process: After adopting new features like code suggestions, take time in retrospectives to evaluate their impact. Gather feedback from your team are PRs merging faster? Is the quality of discussions improving? Use that insight to adjust your workflows. The best practices for your team might evolve as the tools evolve.
By combining these practices with Bitbucket’s new suggestion feature, your team can achieve a faster, more efficient review cycle without sacrificing quality. Code reviews will feel less like a hurdle and more like a seamless extension of your development process.
Bitbucket’s actionable code suggestions represent a significant step forward in developer collaboration. By enabling reviewers to contribute code changes directly and authors to apply them instantly, Atlassian has streamlined a once tedious aspect of software development. Atlas Bench has already been helping teams make the most of this feature, and the results are clear: pull requests get merged quicker, developers spend more time coding and less time waiting, and overall code quality improves thanks to precise, immediate feedback.
If you’re using Bitbucket Cloud, this feature is available for you to use right now. We encourage your team to give it a try on your next pull request. Start with small suggestions and see how much time you save. Once multi-line suggestions roll out, you’ll be ready to tackle larger changes with the same ease.