Add busycal extension

[guidedways]

Description

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! 🚀

We're currently experiencing a high volume of incoming requests. As a result, the initial review may take up to 15 business days.

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

[greptile-apps]

Greptile Summary

This PR adds a new BusyCal extension to the Raycast store with seven commands: structured event/task creation, natural-language quick-add, item search, upcoming items, and a next-available-slot finder backed by BusyCal AppleScript automation.

• The extension is well-structured with proper separation between AppleScript script-building, serialization, installation resolution, and UI layers. Preferences, argument types, and calendar hooks all follow Raycast conventions.
• A copy-paste bug in busycal-command-support.ts causes isDirectMissingBusyCalCommandError to test the identical string in both branches of its || expression, leaving any alternative AppleScript "doesn't understand" phrasing undetected and potentially surfacing raw AppleScript errors to users instead of the friendly version-gate message.
• The CHANGELOG.md initial release entry uses a hardcoded date instead of the required {PR_MERGE_DATE} template placeholder.

Confidence Score: 4/5

Safe to merge after fixing the duplicate condition in the capability-error classifier; the bug affects the user-facing error message for older BusyCal installs, not data integrity.

The duplicate-condition bug in isDirectMissingBusyCalCommandError means users on older BusyCal builds who trigger the Quick Add or item-reveal commands may see a raw AppleScript error rather than the friendly 'BusyCal 2026.1.3 or later is required' message. All other logic — AppleScript generation, serialization, installation resolution, date handling — is sound.

extensions/busycal/src/busycal-command-support.ts — the duplicate OR condition in isDirectMissingBusyCalCommandError.

Important Files Changed

Filename	Overview
extensions/busycal/src/busycal-command-support.ts	Classifies AppleScript capability errors for version-gating; the isDirectMissingBusyCalCommandError function has a copy-paste bug where both branches of the OR check the same string, silently missing alternative error phrasings.
extensions/busycal/CHANGELOG.md	Hardcodes the release date (2026-06-04) instead of the required {PR_MERGE_DATE} template placeholder.
extensions/busycal/src/busycal-automation.ts	All BusyCal AppleScript automation calls (query, create, delete, reveal); logic looks correct and input is properly escaped.
extensions/busycal/src/busycal-installation.ts	Discovers and resolves the active BusyCal install using Spotlight + trusted-root filtering; bundle ID whitelist prevents unintended installs from being targeted.
extensions/busycal/src/busycal-script.ts	AppleScript execution and serialization utilities; retry loop for startup races looks correct, escape/unescape logic is sound.
extensions/busycal/src/busycal-date.ts	Date parsing and formatting; correctly pins locale to en-US and handles floating/all-day/occurrence semantics.
extensions/busycal/src/find-next-available.tsx	Availability lookup form and result detail view; uses command-scoped Preferences type and correctly passes result dates to the event creation form.
extensions/busycal/src/shell.ts	Thin wrappers around execFile/spawn; stdin is always closed after optionally writing payload, which is correct for osascript.
extensions/busycal/src/busycal-hooks.ts	Cached-promise hooks for installation resolution and calendar listing; errors are intentionally suppressed here since they surface via the errorMessage pattern in UI components.
extensions/busycal/package.json	Extension manifest is well-formed with $schema, correct categories, macOS-only platform, and properly typed preferences.

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 2
extensions/busycal/src/busycal-command-support.ts:124-131
**Duplicate condition makes second branch dead code**

Both arms of the `||` in `isDirectMissingBusyCalCommandError` test the exact same string — `"doesn't understand"` — so the second branch is never evaluated independently. The intent was almost certainly to also match a second AppleScript error phrasing (e.g., `"does not understand"` or `"not recognized"`). Because the second variant is missing, any missing-command error that uses a different phrase will not be caught here, causing `isUnsupportedBusyCalCommandError` to fall through its compile-error path and potentially show a raw AppleScript error to the user instead of the friendly "BusyCal 2026.1.3 or later is required" message.

### Issue 2 of 2
extensions/busycal/CHANGELOG.md:3
Changelog entries for new extensions must use the `{PR_MERGE_DATE}` placeholder so the date is set automatically when the PR is merged into the Raycast store. Hardcoding a specific date bypasses this convention.

```suggestion
## [Initial Release] - {PR_MERGE_DATE}
```

_{Reviews (3): Last reviewed commit: "Update CHANGELOG.md and optimise images" | Re-trigger Greptile}

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[guidedways]

I'm waiting for a review, what is 'recent activity'?

[guidedways]

@raycastbot please ask for a review

[guidedways]

@pernielsentikaer any idea how to request a review? Bot thinks this is now stale

[0xdhrv]

issue: metadata image style

The current screenshot has local extension icon in the bottom bar

Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?

Please check the reference on how to take screenshots for extensions.

Reference:

• https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

[0xdhrv]

issue: metadata image style

The current screenshot has local extension icon in the bottom bar

Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?

Please check the reference on how to take screenshots for extensions.

Reference:

• https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

[0xdhrv]

issue: metadata image style

The current screenshot has local extension icon in the bottom bar

Could you make sure that the metadata images use the same background/appearance as the rest to maintain the same visual expression?

Please check the reference on how to take screenshots for extensions.

Reference:

• https://developers.raycast.com/basics/prepare-an-extension-for-store#screenshots

[0xdhrv]

Hey @guidedways 👋

I have added a few comments for you to address.

I'm looking forward to testing this extension again 🔥

Feel free to contact me here or at Slack if you have any questions.

---

I converted this PR into a draft until it's ready for the review, please press the button Ready for review when it's ready and we'll have a look 😊

[raycastbot]

This pull request has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 7 days to keep our backlog clean 😊

[raycastbot]

This pull request has been automatically closed due to inactivity.

Feel free to comment in the thread when you're ready to continue working on it 🙂

You can also catch us in Slack if you want to discuss this.

[guidedways]

@0xdhrv Apologies I just haven't had the time to look into this, can we please keep this open? Or would you prefer when I'm ready I create a new request?

[pernielsentikaer]

Hi @guidedways 👋

I reopened this again 🙂

[guidedways]

Thank you! On it later today :)

[0xdhrv]

Looks good to me, approved ✅

[github-actions]

Published to the Raycast Store:
https://raycast.com/beehive/busycal

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.