[ctawiah]

Context

This layer gives users a direct way to attach an existing LaunchDarkly tool or skill to a variation that is already synchronized in their workspace. The same flow works interactively and through explicit command flags, so it can also be used in non-interactive environments.

What changes

• Adds --attach-tool and --attach-skill to ldcli sync prompt.
• Searches LaunchDarkly for matching tools and skills instead of loading the full catalog locally.
• Lets users search for a project and choose a variation that is already synchronized in the workspace.
• Supports --project and --variation when the caller already knows the target.
• Always fetches the latest tool or skill version before attaching it.
• Saves the attachment file and variation reference together so a failed variation update does not leave an unused file behind.
• Prevents skills from being attached to completion-mode configs because LaunchDarkly only supports them on agent-mode configs.
• Uses one shared attachment flow for tools and skills so another versioned attachment type can follow the same pattern later.

For example:

ldcli sync prompt --attach-tool search-docs
ldcli sync prompt --attach-skill support-guidance --project production --variation support/default

Review focus

• Is the interactive flow clear about selecting a synchronized variation?
• Do explicit flags provide everything needed for non-interactive use?
• Does the command always resolve the latest attachment version before updating the variation?
• Are failed or canceled attachments cleaned up without changing existing local files?
• Is the shared workflow simple enough to extend to another attachment type later?

Verification

• go test ./cmd/sync ./internal/sync/prompt ./internal/sync/local
• go test ./...
• git diff --check

Related changes

Review the stack in this order:

1. Confirm destructive watch actions
2. Guarantee prompt fingerprint convergence
3. Add searchable attachment API foundations
4. Reconcile variation attachments
5. Attach tools and skills to variations
6. Render attachment-aware review output
7. Safely clean unreferenced attachments
8. Persist sync manifests in LaunchDarkly

---

Note

Overview
Adds --attach-tool and --attach-skill to ldcli sync prompt so users can wire the latest LaunchDarkly tool or skill onto an already-synced variation, then run the usual sync pipeline to push changes.

The CLI accepts an explicit key or bare flags for interactive catalog search (SearchAttachments), plus --project and --variation for non-interactive targets. Attachment runs only when a local sync workspace exists, cannot be combined with --add, --detach, --watch, etc., and is cleared on watch retries. attachToVariation reuses existing on-disk attachment content when another variation already references the same tool/skill, rejects skills on completion-mode variations, and updates the local store atomically (failed variation writes roll back new attachment files).

After attach, the command still plans, reviews, and syncs like a normal sync prompt run.

^{Reviewed by Cursor Bugbot for commit 090b7ef. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[ld-ahartmann]

gave this whole stack some ai review and discussion - no negative feedback from my end! seems like everything in here is pretty isolated from the rest of the cli

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{Reviewed by Cursor Bugbot for commit 090b7ef. Configure here.}

[cursor]

Project flag collides with config

High Severity

The new --project flag shares the name of the global default project stored in config and LD_PROJECT. Validate rebinds every command flag from Viper, so a configured project fills --project even when the user omitted it. A normal ldcli sync prompt then fails because --project is treated as an attach-only flag, and attach can also target the wrong project without an explicit flag.

Additional Locations (1)

• cmd/sync/prompt.go#L59-L61

 

^{Reviewed by Cursor Bugbot for commit 090b7ef. Configure here.}