ExportXMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Go Drivers
    • Not Needed
    • None
    • None
    • None
    • None
    • None
    • None

      Context

      We want to see what AI tooling is available internally around code reviews and use it to improve our code review process. One of the first things to try is a custom code review skill for the go driver, but we should identify both what we actually want to get out of code review and do a wide survey of what tooling is available.

      Original Context

      We should run a small pilot of CodeRabbit on the Go Driver repository and assess whether it provides useful signal without adding excessive noise.

      CodeRabbit is reportedly free for open-source support. Their booth at GopherCon also indicated that it uses the latest Anthropic models. These claims should be confirmed as part of the evaluation, along with the applicable usage, privacy, and data-handling terms.

      Definition of done

      • A written doc of pain points / review aspects that seem like they could be made better through the use of AI
      • A list of identified internally available tooling that we want to try incorporating into our workflow (start with Claude)

      Pitfalls

      Not investigated

            Assignee:
            Preston Vasquez
            Reporter:
            Preston Vasquez
            None
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: