> For the complete documentation index, see [llms.txt](https://stepsize.gitbook.io/stepsize-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stepsize.gitbook.io/stepsize-documentation/workflows/using-stepsize-in-your-code-review-process.md).

# Using Stepsize in your code review process

Stepsize provides powerful tools to help your team perform better, faster code reviews.<br>

## **Setting up the GitHub integration**

Our GitHub integration allows you to report tech debt from your pull requests. You can also create GitHub issues from Stepsize issues.

1. Open the [Stepsize web app](https://app.stepsize.com)
2. `Integrations` > `GitHub` > `Connect your GitHub account`

## **Surfacing tech debt in pull requests**

Our pull request tool automatically surfaces issues which relate to the code in the pull request.

This allows the authors and reviewers to assess the potential impact of tech debt on the pushed code.

{% hint style="success" %}
Your team can also use this to prompt discussion on what tech debt to prioritise for fixing.
{% endhint %}

## **Surfacing TODOs and FIXMEs in pull requests**

TODOs are a great single-player tool, but a terrible multiplayer tool. When TODOs make it to `main`, you end up with a never-ending, invisible backlog which isn’t actionable.

Use TODOs to aid your personal code development process. Never merge TODOs into `main`.

Use Stepsize in pull requests to surface TODOs.

![](https://res.cloudinary.com/drvhrxrne/image/upload/v1671458822/samples/product_guides/Screenshot_2022-12-19_at_14.06.56_xsobek.png)

You can create issues from pull requests.

Start your comment with `[stepsize]` to create an issue from a `diff`.

The issue will be automatically linked to the code it relates to, both in your code editor and in the web app.

{% hint style="success" %}
This is a great way to track any tech debt you find during review that your team doesn’t have time to take care of before merging.
{% endhint %}

## **What next?**

We help organisations like yours develop industry-leading tech debt management all the time. Can we help?

## [**Set up a call with us**](https://meetings.hubspot.com/alex527/tech-debt-management-with-alex-stepsize) 🤙


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://stepsize.gitbook.io/stepsize-documentation/workflows/using-stepsize-in-your-code-review-process.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
