Code Review GPT

We give engineers their weekends back

Code Review GPT uses Large Language Models to review code in your CI/CD pipeline. It helps streamline the code review process by providing feedback on code that may have issues or areas for improvement.

It should pick up on common issues such as:

• Exposed secrets
• Slow or inefficient code
• Unreadable code

It can also be run locally in your command line to review staged files.

Code Review GPT is in alpha and should be used for fun only. It may provide useful feedback but please check any suggestions thoroughly.

Demo

https://github.com/mattzcarey/code-review-gpt/assets/77928207/92029baf-f691-465f-8d15-e1363fcb808e

Setup Instructions

See the setup instructions for more information.

Action Usage

See the action documentation for more information.

Getting Started 💫

1. Clone the repository:

   git clone https://github.com/mattzcarey/code-review-gpt.git
   cd code-review-gpt

2. Install dependencies (we use bun but you can use npm or pnpm if you prefer):

   bun i

3. Set up the API key:

   • Rename the .env.example file to .env.
   • Open the .env file and replace YOUR_API_KEY with your actual OPENAI API key.

When used globally you should run export OPENAI_API_KEY=YOUR_API_KEY (or similar for your operating system) in your terminal to set the API key.

To use an OpenAI compatible API, you can set the OPENAI_API_KEY and OPENAI_BASE_URL environment variables and specify the model name when running the review command:

export OPENAI_API_KEY=<YOUR_API_KEY>
export OPENAI_BASE_URL=<YOUR_ENDPOINT>
bun review --model <YOUR_MODEL_NAME>

4. Run the application:

   bun start

See the package.json file for all the npm commands you can run.

5. Make a PR 🎉

We use release-please on this project. If you want to create a new release from your PR, please make sure your PR title follows the Conventional Commits format. The release-please bot will automatically create a new release for you when your PR is merged.

• fix: which represents bug fixes, and correlates to a patch version.
• feat: which represents a new feature, and correlates to a SemVer minor.
• feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version.

Contributors 🙏

Thanks to our wonderful contributors!

Roadmap (see projects tab) 🌏

The roadmap shifts the focus to a Github app which can be installed on any repo. This will allow for a more seamless UX and better features including a chatbot to discuss the PR and make suggestions.

The code-review-gpt package will continue to be maintained and improved based on the feedback from the Github app.

Sponsors ❤️

Star History ⭐️