Hello @jbampton, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request focuses on cleaning up and standardizing the .pre-commit-config.yaml file. The changes primarily involve updating the names and adding descriptions to the hooks used by pre-commit. This aims to improve the readability and maintainability of the configuration file, making it easier for developers to understand the purpose of each hook.

Highlights

• Hook Name Standardization: The names of several hooks have been updated to follow a more consistent run <hook-name> naming convention.
• Hook Descriptions: Descriptions have been added to each hook to clarify its purpose.

Changelog

• .pre-commit-config.yaml
  • Updated hook names to follow the run <hook-name> convention (e.g., detect hardcoded secrets to run gitleaks).
  • Added descriptions to each hook to explain its functionality (e.g., added 'check your identity' description to the identity hook).
  • Minor grammatical change to the markdownlint description, changing 'Checks' to 'checks'.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Trivia time!

What is the purpose of a pre-commit hook?

Click here for the answer
Pre-commit hooks are scripts that run automatically before each commit. They are used to identify and fix issues before code review.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩