Enhance grep-code and post functionality with new prompts and requirements; add .gitignore, .claude.vim, workspace, and links files

[Cleanskiier27]

Summary

Details

Related Issues

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[Cleanskiier27]

vip

[gemini-code-assist]

Summary of Changes

Hello, 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!

This pull request introduces new capabilities for link extraction and content generation within the workspace by enhancing existing commands and adding new ones. It also sets up various configuration files to improve the development workflow and environment setup, particularly for Vim and VS Code users.

Highlights

• Enhanced grep-code functionality: The grep-code command has been significantly updated to specifically find, extract, and transform URL-like references from search results, including converting .net domains to .com.
• New post command introduced: A new post command has been added, designed to generate content from extracted links, ensuring that the links are directly included in the final post while excluding file paths and line numbers.
• Vim configuration and keybindings: A new .claude.vim file was added, providing custom Vim keybindings for efficient navigation, undo/redo operations, and text replacement.
• Development environment setup: Several configuration files were introduced to streamline the development environment, including .gitignore to ignore .env files, fs.code-workspace for VS Code, and gemini-extension.json for custom commands.

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.

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. ↩

[gemini-code-assist]

Code Review

This pull request introduces custom commands and configurations for a file system extension, including Vim settings and link-processing tools. The review identifies critical security vulnerabilities regarding command injection in the PowerShell templates and points out invalid TOML comment syntax that will cause parsing failures. It is recommended to simplify the search logic to improve security and cross-platform compatibility.

[Cleanskiier27]

.thomas