Conversation
kubrickcode
commented
Sep 15, 2025
kubrickcode
commented
- Global extension settings are now managed in the root package.json file.
- The existing extension layer now only manages dependencies specific to the source code.
- Relevant commands, test code, and more have been reworked.
- Global extension settings are now managed in the root package.json file. - The existing extension layer now only manages dependencies specific to the source code. - Relevant commands, test code, and more have been reworked.
|
/gemini review |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @kubrickcode, 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 significantly refactors the project's directory and build structure. The primary goal is to establish a clearer separation of concerns by moving global extension configurations and top-level scripts to the project root, while allowing sub-modules to manage only their immediate dependencies. This reorganization enhances maintainability and simplifies the overall development workflow.
Highlights
- Centralized Configuration: Global extension settings and metadata are now managed in the root package.json.
- Streamlined Extension Dependencies: The src/extension/package.json now exclusively handles dependencies specific to the extension's source code, separating them from global project dependencies.
- Build Process Adjustments: Build and packaging commands in justfile have been updated to reflect the new root-level operations and output directory structure.
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. ↩
There was a problem hiding this comment.
Code Review
This pull request effectively refactors the project structure by moving the main package.json to the root, which centralizes the extension's configuration and build scripts. The changes across justfile, package.json files, and source code paths are consistent with this new structure. My main feedback is regarding the TypeScript configuration, where test files are no longer excluded from compilation, which could lead to including them in the final build artifact.
There was a problem hiding this comment.
Code Review
This pull request refactors the project structure to better manage dependencies and settings by moving global extension configurations to the root package.json. The changes are mostly correct and align with the goal of centralizing the extension's definition. However, I've found one issue in the TypeScript configuration for the extension source that should be addressed.
1 participant
