Skip to content

Conversation

@strantalis
Copy link
Member

Proposed Changes

  • Add AGENTS.md with repo structure and build/lint/test guidance.

Checklist

  • I have added or updated unit tests
  • I have added or updated integration tests (if appropriate)
  • I have added or updated documentation

Testing Instructions

  • make toolcheck (pass)
  • make lint (fails: existing golangci-lint findings)
  • make test (fails: oauth tests require Docker/testcontainers)

@strantalis strantalis requested a review from a team as a code owner January 13, 2026 16:12
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @strantalis, I'm Gemini Code Assist1! 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!

This pull request introduces a new AGENTS.md documentation file to establish clear and comprehensive repository guidelines. The primary goal is to streamline the development process, improve consistency across contributions, and provide a single source of truth for project structure, development commands, coding standards, and contribution practices, thereby enhancing developer onboarding and collaboration.

Highlights

  • New Repository Guidelines Document: A new file, AGENTS.md, has been added to the repository. This document serves as a central guide for contributors, outlining various aspects of development within the project.
  • Comprehensive Development Guidance: The AGENTS.md file covers essential topics including project structure and module organization, standard build, test, and development commands (using make targets), coding style and naming conventions, detailed testing guidelines (unit, BDD, integration), commit and pull request best practices, and security/configuration tips.
  • Standardized Workflow: The new guidelines aim to standardize the development workflow by providing clear instructions on tooling verification (make toolcheck), building (make build), linting (make lint), testing (make test), and local infrastructure setup (docker compose up).

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.


A guide, so clear and bright, For code to shine, day and night. Rules to follow, true, For all developers, old and new.

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The new AGENTS.md file provides a comprehensive overview of the repository's structure, development commands, and guidelines. It's a valuable addition to the documentation, enhancing clarity for contributors.

@strantalis strantalis changed the title docs: add AGENTS.md repo guidelines chore(docs): add AGENTS.md repo guidelines Jan 13, 2026
jp-ayyappan
jp-ayyappan previously approved these changes Jan 13, 2026
@jp-ayyappan jp-ayyappan enabled auto-merge January 13, 2026 17:42
Co-authored-by: Mary Dickson <[email protected]>
Copy link
Contributor

@marythought marythought left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks like a great start!

@jp-ayyappan jp-ayyappan added this pull request to the merge queue Jan 15, 2026
Merged via the queue into opentdf:main with commit de3aa75 Jan 15, 2026
39 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants