skills.rest
daangn
daangnOFFICIAL
Explore all skills by this author →
Website𝕏@daangnteamGitHub

seed-change-plan

Analyzes SEED Design changes to determine impact scope, verification steps, and PR target branch.

1.1k|89|Updated Mar 11, 2021
Search Tags:#verification#Git#impact analysis#Monorepo#changeset#Design system#branch planning
One-click install
npx skills add https://github.com/daangn/seed-design --skill seed-change-plan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seed-change-plan
Source: https://github.com/daangn/seed-design/tree/main/skills/seed-change-plan
Command: npx skills add https://github.com/daangn/seed-design --skill seed-change-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Before implementing changes in the SEED Design monorepo, contributors need to know which packages, components, and platforms are affected, what verification steps to run, and which release branch (dev, minor, or major) the PR should target. This Skill produces that plan in a read-only manner without modifying files, Git state, or remote branches.

Core Features & Use Cases

  • Impact Analysis: Maps changed or planned paths to affected workspace packages, surfaces (source, generated, docs, registry, tests), components, and platforms (React, Lynx, docs, tooling).
  • Verification Planning: Outputs an ordered list of verification steps (generate:all, focused tests, builds, manual runtime checks) with their policy sources, without executing them.
  • Branch Decision Logic: Determines targetBranch, targetRef, and prBase from confirmed changeset bumps, lane evidence against origin/dev, origin/minor, and origin/major, and explicit lane confirmation, returning "unknown" when evidence is incomplete or conflicting.
  • Use Case: A contributor modifying a React component runs the script with --base-ref origin/dev to see impacted packages, required tests, and whether the PR should target dev, minor, or major before handing off to the submission workflow.

Quick Start

Ask the assistant to run the seed-change-plan script with your base ref and changed paths to produce a read-only impact, verification, and target branch plan for your SEED Design change.

Frequently Asked Questions about seed-change-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I determine which branch to target for a SEED Design PR?▼

Run the change-plan script with --base-ref set to the branch your feature forked from. It resolves targetBranch, targetRef, and prBase from confirmed changeset bumps and lane evidence, returning unknown when evidence is incomplete or conflicting.

How do I analyze the impact of a monorepo change before implementing it?▼

Run bun skills/seed-change-plan/scripts/change-plan.ts with --path for specific paths or --planned for files not yet created. The output lists impacted packages, surfaces, components, platforms, and ordered verification steps without executing anything.

Does the change plan script modify files or Git state?▼

No. The script is strictly read-only: it never changes files, Git state, or remote branches, and it does not execute the verification commands it lists. Rebasing, committing, pushing, and PR creation are delegated to the separate seed-submit-change skill.

Why does the branch plan return unknown for my change?▼

The branch is unknown when Git branch evidence is incomplete, lane candidates overlap without an explicit --lane confirmation, a confirmed lane conflicts with the changeset bump, or a publishable package changed without a confirmed bump. Resolve the underlying evidence and rerun.

When should I use --bump versus --no-release flags?▼

Use --bump only after the user confirms a bump through the seed-changeset skill, typically right before final submission. Use --no-release only when the user confirms no changeset is needed, such as for docs, skills, or internal tooling changes.

Can I analyze only specific paths without a base ref?▼

Yes. Pass --path repeatedly to scope the analysis, and omit --base-ref when you only need impact analysis. In that mode the branch decision is not resolved, since branch determination requires Git diff evidence against a base ref.

Related Skills

Explore More Software Engineering Skills→
abnegateabnegate
2

pr

Commit pending changes, push the branch, and create a GitHub pull request.

Community
Intermediate
JacobPEvansJacobPEvans
3

rebase-pr

Rebase pull requests onto main with signed commits and GitHub API checks.

Community
Advanced
saleorsaleor
29

creating-changesets

Automate Changesets semantic versioning workflows in Node.js monorepos with Git and PNPM.

Official
Advanced
Rune-kitRune-kit
82

scope-guard

Compare git changes against a task plan to classify scope creep.

Official
Intermediate