Sign in

Comprehension Coverage

Engineers explain how AI-generated changes affect system behavior. Second Flow turns that understanding into an ownership signal.

Request beta access

northstar/payments-api#482

Prevent duplicate webhook processing

blinktagfix/webhook-deduplication8c4e9d7
src/webhooks/handle-event.ts
31devon-lee export async function handleEvent(event: WebhookEvent) {32devon-lee−  const claimKey = crypto.randomUUID();32blinktag+  const claimed = await dedupeStore.claimOnce(event.id);33blinktag+  if (!claimed) return { status: 202, duplicate: true };34ravi-patel   await dispatch(event);

Duplicate delivery

A repeated event cannot acquire the claim. Why does the handler return 202 instead of dispatching it?

Completed
Choose one response

From changed code to comprehension coverage.

  1. Connect your code

    Install the GitHub App and choose where to add coverage.

  2. Ground the questions

    Second Flow uses the diff, surrounding code, and project context to focus on behavior and intent.

  3. Demonstrate understanding

    The author responds to focused questions about the change's intent, data flow, and effect on system behavior.

  4. Strengthen the review

    Second Flow turns the explanation into a result and returns an ownership signal to GitHub.

The missing signal

A green test suite says the code runs.Understanding the change takes a different kind of coverage.

AI is changing how code gets written. Second Flow makes understanding part of every meaningful change.

Context Gateway grounds every check.

Connect the sources that explain why the change exists and how the repository is meant to behave. Second Flow retrieves only the scoped context needed for each understanding check.

GitHubGitLabBitbucket

Code and change

Pull request, diff, and nearby files

Project documentation

Architecture, runbooks, and product guidance

Work tracking

Intent, requirements, and acceptance criteria

Repository and internal knowledge

Project guidance and approved internal tools

Focused contextContext for this change
  • Changed behavior
  • Repository constraints
  • Why the work exists

Questions shaped by behavior, intent, and project context.

The practical details.

Tests cover execution and code review covers quality. Second Flow adds understanding of intent, data flow, and system impact.

Second Flow focuses on changes with meaningful behavior or context. Small and documentation-only pull requests stay mergeable when no understanding check is needed.

Yes. Second Flow returns a GitHub check that teams can make required through repository rules.

An ownership signal shows your organization how well engineers understand the logic and flow of the AI-generated code they ship.

No. Second Flow reports on submitted explanations, eligible changes, and code areas without creating individual leaderboards. Ownership signals support code review and coaching; they are not a standalone basis for employment decisions.

Context Gateway connects code, project documentation, work tracking, repository guidance, and approved internal tools. It scopes that context to the current change so questions stay relevant.