Finishing Touches overview

One-click agentic actions that polish and extend your pull requests or merge requests: fix review findings, resolve merge conflicts, generate unit tests, simplify code, run any custom recipes.

Finishing Touches are a set of post-review actions that CodeRabbit can perform on your behalf. After a review completes, you can trigger a finishing touch by posting a command in the review conversation and, on supported GitHub flows, by checking a box in the Walkthrough comment. CodeRabbit runs the action in a sandboxed environment and delivers the output as a commit or a follow-up pull request, depending on the action and platform.

Look for the ✨ Finishing Touches section in the CodeRabbit comment; it lists every action available for the current review. If a specific Finishing Touch is not present, it might not be available on your platform or included in your plan (some Touches require ).

Available finishing touches

Autofix |

Automatically implement fixes for unresolved CodeRabbit review findings. Push a commit to your branch or open a stacked pull request.

Fix CI failures |

Investigate failing CI checks and open a stacked pull request with the fixes.

Generate docstrings |

Scan your PR for functions missing documentation and generate format-aware docstrings delivered as a separate PR. Supports 18+ languages.

Resolve merge conflicts |

Detect and resolve merge conflicts by analyzing the intent behind both sets of changes, then commit the result as a proper merge commit.

Generate unit tests |

Analyze your code changes and produce comprehensive unit tests, including edge cases and error conditions, using your project’s existing frameworks.

Simplify code |

Review your changed code for opportunities to simplify, improve reuse, quality, and efficiency, then apply targeted improvements automatically.

Custom recipes |

Define reusable, named recipes in your config that encode your team’s repeated tasks: import ordering, type tightening, changelog entries, and more.

Platform support

Platform	Available finishing touches
GitHub	Autofix, Fix CI failures, Generate docstrings, Resolve merge conflicts, Generate unit tests, Simplify code, Custom recipes
GitLab	Autofix, Generate docstrings, Resolve merge conflicts, Generate unit tests, Custom recipes
Azure DevOps	Autofix, Generate docstrings
Bitbucket Cloud	Autofix, Generate docstrings
Bitbucket Data Center	Generate docstrings

How to trigger

Available triggers depend on the feature and platform:

Method	How	Where
Review comment	Comment a command like @coderabbitai generate docstrings	Supported command-capable platforms for that Finishing Touch
Checkbox	Check the box in the ✨ Finishing Touches section of the CodeRabbit Walkthrough comment	GitHub PRs

See each feature page for the exact commands and platform support details.

Quick reference

Finishing touch	Trigger	Output
Generate docstrings	@coderabbitai generate docstrings	New pull request with docstrings
Generate unit tests	@coderabbitai generate unit tests or GitHub checkbox	Pull request or commit on branch
Simplify code	GitHub checkbox	New pull request or commit on branch
Autofix	@coderabbitai autofix	Commit on branch or stacked pull request
Fix CI failures	@coderabbitai fix-ci	Stacked pull request with fixes
Custom recipes	@coderabbitai run <recipe name> or GitHub checkbox	Stacked pull request by default; direct commit when the recipe explicitly asks for one
Resolve merge conflicts	@coderabbitai fix merge conflict	Merge commit on branch

What’s next

Autofix

Automatically implement fixes for unresolved review findings and push them as a commit or stacked pull request

Custom recipes

Define reusable, named recipes that encode your team’s repeated tasks into one-click agentic actions

Resolve merge conflicts

Let CodeRabbit analyze the intent behind conflicting changes and commit a clean resolution to your branch