repo-sensei

Product

Fix

Hand it a stack trace, a GitHub issue or an error Sentry saw. It finds the cause, proves it with a failing test, and proposes a patch you approve, verified by the tests.

How a fix runs, stage by stage

  1. Intake (done)
  2. Investigate (done)
  3. Reproduce (done)
  4. Root cause (done)
  5. Plan (done)
  6. Approve (done)
  7. Patch (done)
  8. Verify (current)
  9. PR (to come)
  1. 1

    Intake

    The trace, issue or Sentry error is read into frames in your code.

  2. 2

    Investigate

    An agent reads the code and its history to find the cause.

  3. 3

    Reproduce

    It writes a test that fails for that reason, and runs it three times.

  4. 4

    Root cause

    What else the cause reaches, from the code's graph.

  5. 5

    Plan

    The files and steps of the fix, with its risk.

  6. 6

    Approve

    People with write access approve it, ask for changes, or reject it.

  7. 7

    Patch

    The plan is carried out in the sandbox, file by file.

  8. 8

    Verify

    The whole suite runs again, and the patch is checked for gaming.

Opening the pull request on your repository, with the patch, its test and the evidence, is coming soon.