[example] An email search workflow#230
Merged
pan-x-c merged 16 commits intoagentscope-ai:mainfrom Aug 29, 2025
Merged
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Summary of Changes
Hello @hiyuchang, 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 example workflow for email search, leveraging a ReAct-style agent and a SQLite database populated with email data. It provides the necessary configurations, data preparation scripts, and agent implementations to enable an AI model to search and read emails.
Highlights
- New Email Search Workflow: Implemented EmailSearchWorkflow to enable multi-turn email search using a ReAct-style agent.
- Dedicated Agent with Tools: Introduced EmailSearchAgent equipped with search_emails and read_email tools for interacting with an email database.
- Email Data Management: Added prepare_data.py to download, create, and populate a SQLite database with email information, including full-text search capabilities.
- Workflow Configuration: Provided new YAML configuration files (email_search.yaml, train_email_search.yaml) to define the setup for the email search project, including model paths, data sources, and training parameters.
- Utility Functions: Included utils.py with data models and helper functions for email handling, search result formatting, and LLM-based correctness judging.
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 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.
Footnotes
-
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. ↩
Contributor
There was a problem hiding this comment.
Code Review
This pull request introduces a new email search workflow example, including data preparation scripts, configuration files, and the workflow implementation itself. The implementation uses a ReAct-style agent with tool use capabilities to interact with a simulated email database.
My review focuses on improving code robustness, maintainability, and configuration. Key suggestions include:
- Making configuration more flexible by avoiding hardcoded paths and values.
- Improving error handling, especially around database connections and optional dependencies.
- Enhancing code clarity and adhering to best practices, such as using
withstatements for resources and ensuring docstrings match function signatures. - Filling out placeholder documentation to make the example easier to use.
yanxi-chen
reviewed
Aug 28, 2025
Collaborator
Author
|
/unittest-all |
Summary
Tests
Github Test Reporter by CTRF 💚 |
pan-x-c
approved these changes
Aug 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
As tht title says.
Checklist
Please check the following items before code is ready to be reviewed.