Add conductor extension

[mblode]

Description

Adds a Conductor extension with two commands:

• Search Workspaces: search local Conductor workspaces from the database, show a working spinner when a session is active, and open in Conductor or an editor.
• List Repositories: browse repos, drill into per-repo workspaces, and create a new workspace by opening a repo in Conductor.

Requires Full Disk Access to read Conductor’s local database. macOS only.

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

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.

[greptile-apps]

Greptile Summary

Added new Conductor extension with two view-type commands: Search Workspaces and List Repositories, both reading from Conductor's local SQLite database.

• Well-structured SQL querying with proper escaping and permission handling
• Clean component architecture with reusable workspace/repository list items
• Proper macOS platform specification and Full Disk Access requirement documented
• Missing required metadata/ folder with Raycast-styled screenshots - blocking issue for store submission
• CHANGELOG could be more descriptive about features added

Confidence Score: 3/5

• Generally safe implementation with one blocking metadata requirement
• Code quality is excellent with proper SQL escaping, permission handling, and React patterns. However, the PR is missing the required metadata/ folder with screenshots, which is mandatory for extensions with view-type commands per store guidelines. This must be resolved before store submission.
• The package.json needs accompanying metadata folder creation, though the code itself is production-ready

Important Files Changed

Filename	Overview
extensions/conductor/package.json	Configuration is clean but missing required metadata folder for view-type commands
extensions/conductor/src/search-workspaces.tsx	Well-structured workspace search with proper SQL querying, permission handling, and UI components
extensions/conductor/src/list-repositories.tsx	Clean repository listing with nested workspace views, proper actions and navigation
extensions/conductor/CHANGELOG.md	Changelog format is correct but could include more detail about changes

[greptile-apps]

Additional Comments (1)

1. extensions/conductor/package.json, line 15-30 (link)

   logic: Missing metadata/ folder with Raycast-styled screenshots. Extensions with view-type commands require professional screenshots in the metadata folder.

   Create a metadata/ folder and add Raycast-styled screenshots following the documentation: https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

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

_{9 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Additional Comments (2)

1. extensions/conductor/package.json, line 15-30 (link)

   logic: missing required metadata/ folder with Raycast-styled screenshots for view-type commands

   Per extension guidelines, all extensions with view-type commands must include a metadata/ folder containing Raycast-styled screenshots. This PR adds two view-type commands but doesn't include the required metadata folder.

   Create: extensions/conductor/metadata/ with properly formatted screenshots.

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

2. extensions/conductor/CHANGELOG.md, line 3 (link)

   style: changelog entry needs description of changes

   Changelog entries should describe what features or changes were added. This should include a brief description of the two commands being added.

   Good example:

   ## [Initial Version] - {PR_MERGE_DATE}
   
   - Added Search Workspaces command
   - Added List Repositories command
   

   ... (source)

   _{Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!}

   Context Used: Rule from dashboard - What: Ensure that CHANGELOG.md is created or updated with relevant changes for every pull request.

_{9 files reviewed, 2 comments}

_{Edit Code Review Agent Settings | Greptile}