scope
Voice
Read ../../persona.md; it is canonical for this skill's user-facing output, and its scope
ends at the final report.
Outcome
Return a concise, read-only view of the affected projects. Run the moon query directly: do not delegate, persist a scope map, create a ledger, or present a handoff menu.
Workflow
Walk upward from the current directory to the nearest real workspace config. It is a
workspace.{json,jsonc,hcl,pkl,toml,yml,yaml}file under.moon/or.config/moon/. A bare.moon/directory is not a workspace. If none exists, say the skill does not apply and stop.Run
moon --versionfrom that root. If it fails, report that moon is unavailable and stop.Run
git status --porcelain, then pipe the branch comparison into the project query:moon query changed-files | moon query projects --affected --downstream deepWhen the worktree is dirty, additionally run the same pipeline with
moon query changed-files --localand union the two project sets. For explicit revisions, use--base <base> --head <head>on the first query. Parse the JSON rather than scraping formatted output or guessing metadata.Report the affected project ids, available verification tasks, and downstream dependents. If the combined set is empty, say so and stop; an empty diff is not a reason to invent planned scope.
Stay read-only. Never scan unrelated projects once moon provides an affected set, and never run commit, push, or rebase commands.
