[ctawiah]

Context

Since #939, the sync code has a scope: prompts, tools, skills, or all. Only the sync uses it, through SyncAction. So add and detach always work on variations, and every message talks about prompts. This PR routes sync, add, and detach by scope, so that the next PR only adds the commands.

What changes

• Scope moves from SyncAction to Options, so that every action gets it. AddAction.Variations becomes Resources.
• In a repository without sync files, sync all fails with Nothing to sync in this repository. To start, run ldcli sync prompts add, ldcli sync tools add, or ldcli sync skills add.
• In such a repository, a sync of tools or of skills starts the add of that kind, as a sync of prompts does today.
• Add and detach use the kind of the scope.
• Without a terminal, the conflict error names --resolve only in the prompts scope, because only sync prompts has it.
• An empty plan names the add of the scope, for example No tools are synced in this repository. To start, run ldcli sync tools add.
• A prompts plan notes the tool and skill files that it leaves out:

Note: 1 standalone skill and 1 standalone tool are not in this plan. Run ldcli sync all to include them.

• A sync of tools or skills does not write variations. So after it pushes a tool, a note names each local variation that uses the tool:

Note: Prompt production/support/default uses tool search. It repins on the next ldcli sync prompts or ldcli sync all.

Design notes

• The standalone count reads only paths (ParseManagedPath), so an invalid standalone file never breaks sync prompts. Only a prompts plan counts. A tool or skill with a row in the plan, for example a row from the first PR of this stack, is not counted.
• Tool and skill rows get an unexported usedBy, set in the same loop that sets SyncedElsewhere. The repin note is its only user. The other option, a second compile of the variations after the apply, reads the files twice.
• applyConflictResolutions now copies the rows of the plan before it changes them, so the reviewed plan stays as it was.
• This PR must ship in the same ldcli release as feat: apply tool and skill rows in a sync #941, with the previous PR and the next PR, which adds the commands.

Review focus

• Does every message name a command that exists in its scope?
• Is the standalone count right with a filter, and with a tool that has a row?

Verification

• go test ./... and golangci-lint run (v2.9.0) pass.
• New acceptance tests through Runner.Run:
  • a workspace with only one tool
  • the standalone count, with no read of the counted files
  • no count for a tool that has a row
  • a repository without sync files, in each scope
  • add and detach of tools
  • a shared tool conflict that a sync of that one tool resolves, after which the next sync of every kind only repins the variation
• TestWritePlanReviewNamesTheAddOfAnEmptyScope checks the empty-plan message of each scope.

Related changes

This stack builds on #937 to #941, which are merged.

1. fix: exclude expanded tools from prompt diffs #957: Exclude expanded tools from prompt diffs (ctawiah/fix-prompt-tool-diff-5b1c)
2. fix: plan a tool or skill row when a variation newly references it #945: Plan a tool or skill row when a variation newly references it (ctawiah/plan-referenced-attachments-1e8a)
3. feat: keep unused tools and skills, and detach any resource kind #946: Keep unused tools and skills, and detach any resource kind (ctawiah/keep-unused-attachments-1e8a)
4. feat: add tools and skills from LaunchDarkly #947: Add tools and skills from LaunchDarkly (ctawiah/add-attachments-1e8a)
5. This PR: route sync, add, and detach by scope (ctawiah/route-scopes-1e8a)
6. feat: add the sync all, sync tools, and sync skills commands #949: Add the sync all, sync tools, and sync skills commands (ctawiah/scope-commands-1e8a)
7. feat: create a tool or a skill from the content of an add #950: Create a tool or a skill from the content of an add (ctawiah/create-attachments-1e8a)
8. feat: add the create flags of sync tools add and sync skills add #951: Add the create flags of sync tools add and sync skills add (ctawiah/create-attachment-flags-1e8a)
9. refactor: share the selection of a new variation, and check any kind before an add #952: Share the selection of a new variation, and check any kind before an add (ctawiah/share-variation-selection-1e8a)
10. feat: create a prompt variation from the content of an add #953: Create a prompt variation from the content of an add (ctawiah/create-variations-1e8a)
11. feat: add the create flags of sync prompts add #954: Add the create flags of sync prompts add (ctawiah/create-variation-flags-1e8a)

---

Note

Overview
Sync, add, and detach are driven by command scope instead of carrying scope only on SyncAction. Scope lives on Options; AddAction uses a generic Resources list validated against the scope’s resource kind.

Empty-repo and messaging behavior is scope-aware: sync all errors with a combined “nothing to sync” hint; scoped tool/skill sync can bootstrap an add. Empty plans, filter errors, and non-interactive conflict messages point at the right ldcli sync … commands (--resolve only for prompts).

Prompt-only plans count standalone tool/skill files (path-only, respecting filters) and print notes that they’re excluded unless you run sync all. Tool/skill syncs don’t write variations; after a successful push, repin notes tell users to run sync prompts or sync all. Plans track usedBy for that flow.

Conflict resolution copies the plan before mutating rows so the reviewed plan stays intact. Acceptance tests cover scoped sync, standalone counts, add/detach tools, and shared tool conflicts.

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

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Add/detach error still names variations

Low Severity

validateSelections now takes a kind so add and detach work for tools and skills, but the error still tells the user to pass variations via --config-key and project-key/config-key/variation-key. Mixing positional selectors with target flags in a tools or skills command therefore names a selector that does not exist in that scope.

 

^{Reviewed by Cursor Bugbot for commit 84d0406. Configure here.}

[cursor]

Only sync prompts add and sync prompts detach take positional selectors. The tool and skill commands use cobra.NoArgs and reject one as an unknown command, so this check only runs in the prompts scope, where the variation wording is right.

[cursor]

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

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 000e9ee. Configure here.}