Introduction

Second Flow helps engineers explain meaningful code changes and gives teams an ownership signal.

AI makes code faster to write. Engineers still need to understand how that code changes system behavior. Second Flow adds an understanding check to the code-review workflow so authors can explain the intent, logic, and impact of their changes.

Tests cover execution and code review covers quality. Second Flow adds understanding of the change.

How it works

1. Connect GitHub and make the repositories you want to use accessible to Second Flow.
2. Configure the repository’s understanding policy and selected project context.
3. For an eligible pull request, Second Flow generates questions grounded in the diff, surrounding code, and available project context.
4. The author follows the check link, signs in, and submits an explanation.
5. Second Flow creates a result and returns an ownership signal to the repository.

What you can do

• Get started with a repository and your first understanding check.
• Complete an understanding check and review its result.
• Configure an understanding policy for your repository.
• Select project context to ground questions in repository guidance.
• Read ownership signals across the workspace.

Private beta

Second Flow is in private beta. Access and provider availability depend on your workspace. Contact us to request access or get help with setup.