Open Source Go Code Review Software

Open Code Review is an AI-powered command-line code review tool. It originated from Alibaba’s internal AI review assistant and was later released as an open-source project for broader developer use. The tool reads Git diffs, analyzes changed files, and generates structured review comments with line-level precision. It is designed to go beyond shallow diff feedback by letting the agent inspect full files, search the codebase, and use surrounding context. Developers can configure model endpoints, making it adaptable to different LLM providers and deployment needs. Its main value is bringing large-scale, agent-assisted review workflows into local and CI-based development environments.

As Chroma has just been released, its API is still in flux. That said, the high-level interface should not change significantly. Chroma takes source code and other structured text and converts it into syntax-highlighted HTML, ANSI-coloured text, etc. Chroma is based heavily on Pygments and includes translators for Pygments lexers and styles. ABAP, ABNF, ActionScript, ActionScript 3, Ada, Angular2, ANTLR, ApacheConf, APL, AppleScript, Arduino, Awk. PacmanConf, Perl, PHP, PHTML, Pig, PkgConfig, PL/pgSQL, plaintext, Pony, PostgreSQL SQL dialect, PostScript, POVRay, PowerShell, Prolog, PromQL, Properties, Protocol Buffer, PSL, Puppet, Python 2, Python. Lexers convert source text into a stream of tokens, styles specify how token types are mapped to colours, and formatters convert tokens and styles into formatted output. A package exists for each of these, containing a global Registry variable with all of the registered implementations.

This repo contains a command-line tool for performing code reviews on git repositories. This tool is a distributed code review system for git repos. By "distributed", we mean that code reviews are stored inside of the repository as git objects. Every developer on your team has their own copy of the review history that they can push or pull. When pulling, updates from the remote repo are automatically merged by the tool. This design removes the need for any sort of server-side setup. As a result, this tool can work with any git hosting provider, and the only setup required is installing the client on your workstation. he git command-line tool is configured with the credentials it needs to push to and pull from the remote repos. The code review data is stored in git-notes, using the formats described below. Each item stored is written as a single line of JSON, and is written with at most one such item per line.

Gnomock is an integration and end-to-end testing toolkit. It uses Docker to create temporary containers for application dependencies, set up their initial state and clean them up in the end. Gnomock allows to testing the code with no mocks wherever possible. The power of Gnomock is in a variety of Presets, each implementing a specific database, service, or other tools. Each preset provides ways of setting up its initial state as easily as possible: SQL schema creation, test data upload into S3, sending test events to Splunk, etc.

Reviewpad is a service to automate pull requests and issues workflows. The workflows are specified in a YML-based configuration language described in the official documentation. In Reviewpad, you can automate actions over the pull requests and issues. With technological progress depending on the human ability to create and modify software systems, Reviewpad was founded to allow developers to safely contribute to any codebase as fast as possible. Developers deserve a better experience and that goal is what has driven our work at Reviewpad. At the core of this experience is security – developers should be able to go faster without increasing the risk of introducing changes that can hurt their products, users, and organizations.

I’d like to introduce reviewdog! An automated code review tool working with any lint tools and supports local run as well. “reviewdog” provides a way to post review comments to code hosting services, such as GitHub, automatically by integrating with any linter tools with ease. It uses any output of lint tools, with translation if required, and posts them as a comment if the file and line are in diff of patches to review. reviewdog also supports running in a local environment to filter the output of lint tools by diff. We can use various linters and static code analysis tools to detect such problems in local machines, editors, CI services. However, here is the problem. Static analysis tools may report false-positive results. Reporting false-positive results itself is ok, but due to the false-positive results we cannot make build fail and it becomes difficult for us to find true positive results from messed up analysis results.