Skip to content

Conversation

@dmdque
Copy link

@dmdque dmdque commented Jan 7, 2026

Description

A Raycast extension that generates CLI commands and code snippets from natural language. Inspired by Cursor's Cmd+K.

command-generator-1

Screencast

https://www.loom.com/share/0c62deccedc847288395260e0f292b73

Checklist

- Improvements and prep for submission
- Prep for publishing
- Add model selection: Claude Haiku 4.5 or Gemini Flash 2.5 Lite
- Improve prompt quality and fix history selection UX
- Add context awareness (selected text, app, directory)
- Simplify history selection UX
- Raycast CLI command generator
@raycastbot raycastbot added new extension Label for PRs with new extensions platform: macOS labels Jan 7, 2026
@raycastbot
Copy link
Collaborator

Congratulations on your new Raycast extension! 🚀

Due to our current reduced availability, the initial review may take up to 10-15 business days.

Once the PR is approved and merged, the extension will be available on our Store.

dmdque added 2 commits January 7, 2026 20:46
- Remove conflicting react package
- Move screenshots into folder
@dmdque dmdque marked this pull request as ready for review January 7, 2026 13:08
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Jan 7, 2026

Greptile Summary

This PR adds a new command-generator extension that uses AI models (Gemini 2.5 Flash-Lite or Claude Haiku 4.5) to generate CLI commands and code snippets from natural language descriptions. The extension captures context from the active application, selected text, and current directory to provide more relevant suggestions.

Key changes:

  • Implements context-aware command generation with support for Terminal, iTerm, and various IDEs
  • Provides prompt history with filtering and reuse functionality
  • Offers two action modes: paste directly or copy to clipboard

Issues found:

  • Manual Preferences interface definition should be removed (auto-generated by Raycast)
  • Screenshots are in screenshots/ folder but must be in metadata/ folder per Raycast guidelines

Confidence Score: 4/5

  • This PR is safe to merge after addressing the two configuration issues
  • The implementation is well-structured and functional, but has two violations of Raycast extension guidelines: manual Preferences interface definition and incorrect screenshot folder location. Both are straightforward fixes that don't affect core functionality.
  • Pay close attention to src/generate-command.tsx (remove manual interface) and move screenshots from screenshots/ to metadata/ folder

Important Files Changed

Filename Overview
extensions/command-generator/package.json Standard configuration file with proper preferences setup and dependencies
extensions/command-generator/src/generate-command.tsx Main component with manual Preferences interface that should be auto-generated; otherwise well-structured

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

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

Additional Comments (2)

  1. extensions/command-generator/src/generate-command.tsx, line 20-24 (link)

    syntax: Remove manual Preferences interface - it's auto-generated in raycast-env.d.ts

    Context Used: Rule from dashboard - What: Don't manually define Preferences for getPreferenceValues() or commends Argument interfa... (source)

  2. extensions/command-generator/package.json, line 15-21 (link)

    syntax: Screenshots must be in metadata/ folder, not screenshots/ folder. View-type commands require Raycast-styled screenshots in the metadata/ directory.

    Context Used: Rule from dashboard - What: Extensions with view-type commands must include a metadata/ folder containing Raycast-styled... (source)

7 files reviewed, 2 comments

Edit Code Review Agent Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

new extension Label for PRs with new extensions platform: macOS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants