Scope migration stop-and-ask rules to dependent operations

Open Beginner friendly
#87 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
92/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Open skills/sanity-migration/SKILL.md and review the Stop and Ask section. Update the rules so independent local transformation and validation can continue when remote credentials are missing, while dependent connection and import remain paused. Confirm the acceptance example: a local fixture and agreed schema allow NDJSON preparation and validation without enabling remote import.

Written by the indexing model from the issue text.

Description

Problem

The Stop and Ask section in skills/sanity-migration/SKILL.md says to stop before coding when source credentials or the target project/dataset are unclear.

This blocks useful local preparation even when the user supplies a source fixture and requests an offline transformation. Credentials and a selected remote dataset are not needed for that work.

Example

A user supplies a Markdown export, specifies the target document shape, and asks for an NDJSON transform with local validation. Sanity credentials will be provided later.

Expected: prepare and validate the local transform; defer remote connection and import until their prerequisites are available.

Current instruction: stop before coding because credentials or target details are missing.

Suggested wording

Use information already supplied. Ask only for missing facts that materially affect the next step. Pause the dependent connection, import, or schema decision while continuing independent local preparation.

Keep the existing checks for content scope, media, schema, and destination. Apply each check before the operation that depends on it.

Acceptance example

With a local fixture and an agreed schema, missing remote credentials should permit local transformation and validation while blocking remote import.

Dominant language
JavaScript
Stars
185
Forks
29
Avg merge
1d 6h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sanity-io/agent-toolkit

All issues in sanity-io/agent-toolkit

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.