seed-change-plan

SEED change plan

Read the current checkout to first confirm the work impact and verification order. This skill does not change files, Git state, or remote branches, nor does it execute the planned commands.

Procedure

1. Run the following script from the repository root.

   bun skills/seed-change-plan/scripts/change-plan.ts --base-ref origin/dev
   

   --base-refspecifies the base from which the current feature branch actually diverged. Before rebasing, use the existing base branch, and only when re-running finally after completing the rebase, use the confirmed targetRef. For files not yet created, add them with --planned <저장소 상대 경로>. When analyzing only specific paths, repeat --path, and in this case, if only impact analysis is needed, --base-refmay be omitted.

2. impact, check the following items.

   • packages: workspace packages directly affected
   • surfaces: classification as source, artifact, implementation, documentation, example, test, release, or tooling
   • components, platforms: components and React·Lynx impact

1. verificationin the order shown. For each step, use sourceto check whether the item comes from root policy, package scripts, a delegated skill, or a manual check. Do not execute during the planning stage.

2. branchEvidenceis complete.

   • complete가 falseor if there is errors, then regardless of bump or --no-release, the branch is unknown.
   • When implicitly collecting Git changes, if there is no --base-ref, do not confirm the branch.
   • rename preserves both the old and new paths. Public packages that have disappeared from the current checkout are checked with baseRef의 package.json.

3. laneCandidatesis only a candidate that overlaps in path with branch-specific work and is not confirmation evidence. If there is a candidate, directly check both diffs.

   git diff --name-status origin/dev...origin/minor -- <후보-경로>
   git diff --name-status origin/dev...origin/major -- <후보-경로>
   

   Depending on the check result, re-run with one of --lane minor, --lane major, --lane none . Do not automatically select a lane based only on candidates.

4. branch.targetBranch, targetRef, prBaseare all the same.

   • As a result of direct checking, if you modify unreleased work in minor나 major, specify that lane.
   • Otherwise, set it to the highest value among the confirmed bumps. patch는 dev, minor는 minor, major는 major.
   • Documentation, skill, and internal tooling changes with no release are dev.
   • If branch-specific evidence and the bump conflict, or if the bump of a published package is unconfirmed, it is unknown.

5. Before confirming the bump, do not include --bump. After the user confirms the bump with seed-changeset, re-run it just before final submission. Only if the user has confirmed that no changeset is needed, use --no-release.

6. confirmed targetRef와 prBase를 seed-submit-changehanded over to. The submission skill must perform rebase, commit, push, and PR creation or update on the same basis.

Boundary

• unknownis not changed to an arbitrary branch.
• laneCandidatespath intersection is not used as grounds for branch confirmation.
• origin/dev, origin/minor, origin/majoreven if the SHA is the same, the selected branch name is not changed to another name.
• If a generated artifact path is visible, check the corresponding source and bun generate:all, and do not directly modify the generated artifact.
• Command execution and result determination are handled by the agent's default shell. Session baseline, log storage, and failure fingerprint classification are not created.
• Rebase, commit, push, and PR creation/update are handled by seed-submit-change.