feat: add go cli

[marcelosousa]

Description

This pull request introduces a Go CLI

Closes #3.

Type of change

New feature (non-breaking change which adds functionality)

Checklist

• I have performed a self-review of my code

Code review and merge strategy (ship/show/ask)

Ask: this pull request requires a code review before merge

[reviewpad]

AI-Generated Pull Request Summary: This pull request adds a new Go CLI with the following changes:

• It modifies the .gitignore to only ignore the ai-preview binary.
• It creates three new command files: commit-msg.go, init.go, and root.go in the cmd package.
• It adds a new Go module with the required dependencies: github.com/reviewpad/go-conventionalcommits, and github.com/spf13/cobra.
• It creates a new go.sum file with the dependency checksums.
• Additionally, it creates a main.go file that executes the CLI.

The CLI itself seems to offer commands for checking if a commit message respects the conventional commits format and for installing git hooks.

[reviewpad]

Thank you @marcelosousa for this first contribution!

[marcelosousa]

/reviewpad summarize

[reviewpad]

AI-Generated Pull Request Summary: This pull request introduces a new CLI tool in Go that adds support for checking if commit messages follow the conventional commits format. It also sets up basic CLI infrastructure using the Cobra library and installs Git hooks. Specifically, the changes include:

• Adding new command files commit-msg.go, init.go, and root.go.
• Creating a new Go module with required dependencies, including the go-conventionalcommits and cobra libraries.
• Updating the .gitignore file.
• Implementing the commit-msg command to check and lint commit messages.
• Implementing the init command to install the Git hooks.
• Adding the main entry point file main.go for the CLI application.

[marcelosousa]

/reviewpad robin prompt is there any security vulnerabilities in this code?

[reviewpad]

From the provided patch, I don't see any apparent security vulnerabilities in the code. However, it is important to note that a comprehensive security review should involve more in-depth analysis, potentially including static code analysis and dynamic testing. Also, keep your dependencies up-to-date to mitigate any security risks that may be inherent in the third-party libraries used in your project.