explica.dev

Explain your change.Ship with confidence.

Explica turns meaningful GitHub pull requests into diff-grounded understanding checks, then returns each result as an ownership signal your team can use in review.

Request beta access

Authors respond from a private link without creating an account.

northstar/payments-api#482

Make webhook retries idempotent

blinktagfix/webhook-replay8c4e9d7

Understanding check

Explain the change you are submitting.

Your responses show how you understand the behavior and implications of this pull request.

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 };

Request identity

Why does the handler pass event.id to claimOnce instead of generating a new key?

Completed
Choose one response

Inside code review

One path from pull request to ownership signal.

  1. Connect GitHub

    Install the GitHub App and choose the repositories to cover.

  2. Ground the check

    The diff, nearby code, and connected context shape each question.

  3. Submit an explanation

    The author responds through a private ownership link.

  4. Publish the signal

    Explica returns the result to GitHub for review or enforcement.

The missing signal

A green test suite says the code runs.It does not say the author understands why.

Reviewers can inspect the diff. Explica checks the thinking behind it inside the pull request workflow the team already uses.

Context Gateway

Pull the right context into every check.

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

GitHubGitLabBitbucket

Code and change

Pull request, diff, and nearby files

VCS

Project documentation

Architecture, runbooks, and product guidance

Docs

Work tracking

Intent, requirements, and acceptance criteria

Issues

Repository and internal knowledge

Project guidance and approved internal tools

Custom
Bounded snapshotContext for this change
  • 01Changed behavior
  • 02Repository constraints
  • 03Why the work exists

Grounded understanding check with source-aware questions and rubrics.

Questions, answered

The practical details.

No. Your reviewers and CI still own code quality. Explica checks whether the author understands the behavior and implications of their change.

Explica skips changes that cannot support a useful question. It leaves a clear PR comment and reports a neutral check, so the pull request stays mergeable.

Yes. Set the standard your team expects and make the Explica check required through your GitHub repository rules.

No. Authors open a private ownership link from the pull request and submit their explanation without signing in to the console.

Context Gateway brings selected project documentation and operational context into check generation. The private beta will begin with a focused provider set and add more connections over time.

Private beta

Make understanding part of the merge.

Bring Explica to your GitHub organization and help shape the Context Gateway, understanding checks, and signals your team will use.

Request beta access