Skip to content

Structsense getting started#17

Merged
tekrajchhetri merged 6 commits intomainfrom
structsense_getting_Started
Nov 7, 2025
Merged

Structsense getting started#17
tekrajchhetri merged 6 commits intomainfrom
structsense_getting_Started

Conversation

@tekrajchhetri
Copy link
Copy Markdown
Collaborator

This pull request creates a separate subsection LLM under Requirements.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @tekrajchhetri, 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 enhances the StructSense documentation by creating a dedicated section for Large Language Model (LLM) configurations. This change centralizes details about using OpenRouter and Ollama for agents and embeddings, improving the clarity and organization of the getting started guide. By consolidating this information, the PR aims to provide a more streamlined and accurate resource for users setting up LLM components within StructSense.

Highlights

  • Documentation Structure: A new 'LLM' subsection has been introduced under 'Requirements' in the structsense_getting_started.md document to centralize information regarding Large Language Models.
  • LLM Configuration Details: The new section clarifies the roles of OpenRouter and Ollama for both agent functionality and embedding generation, providing guidance on their usage.
  • Documentation Refinement: Redundant information about Ollama's role in embedding generation has been removed from the 'docker/' section of structsense_getting_started.md to avoid duplication and improve clarity.
  • Minor Formatting Adjustment: A small formatting change was made to the 'Quickstart' heading in structsense_overview.md by adding a trailing space.
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.

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
Copy Markdown
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

This pull request refactors the documentation by creating a dedicated LLM subsection within the Requirements section of the getting started guide. The changes improve the document's structure. My review includes a few suggestions to enhance clarity and fix minor formatting issues in the markdown files for better readability and consistency.

Comment thread docs/structsense_getting_started.md Outdated
Comment thread docs/structsense_getting_started.md Outdated
Comment thread docs/structsense_overview.md Outdated
tekrajchhetri and others added 3 commits November 7, 2025 14:55
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@tekrajchhetri tekrajchhetri merged commit 271723f into main Nov 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant