chore: restructure storybook-sync skill and add .agents/skills layout

Move skill from .claude/skills/storybook-sync-checker to .agents/skills/storybook-sync
with a symlink at .claude/skills, matching the rstest repo convention.

Refactor SKILL.md: move priority criteria before workflow, flesh out
direct analysis steps, parameterize example commands, add issue
creation step.

Author: fi3ework

…e/skills/storybook-sync-checker/SKILL.md .agents/skills/storybook-sync/SKILL.md.claude/skills/storybook-sync-checker/SKILL.md renamed to .agents/skills/storybook-sync/SKILL.md .claude/skills/storybook-sync-checker/SKILL.md renamed to .agents/skills/storybook-sync/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: storybook-sync-checker
+name: storybook-sync
 internal: true
 description: Check and analyze upstream Storybook repository changes that may need to be synced to storybook-rsbuild. Use this skill whenever the user wants to check for upstream Storybook changes, review what's new in the official Storybook repo, identify changes needing sync, or compare storybook-rsbuild against the upstream. Activate for phrases like "check upstream", "sync check", "storybook changes", "need to sync", "what changed upstream", or any mention of tracking changes from storybookjs/storybook. Even casual mentions like "anything new in storybook?" should trigger this skill.
 ---
@@ -26,63 +26,86 @@ Analyze recent changes in the official `storybookjs/storybook` repository and id
 
 Both webpack5 and vite upstream variants are monitored because this repo borrows patterns from both.
 
-## Important: Upstream Commit History is Noisy
+## Upstream Commit History is Noisy
 
-The Storybook repo uses a **non-linear branching model** with frequent merge commits and automated version bumps. The bundled script already handles the most common noise:
+The Storybook repo uses a non-linear branching model with frequent merge commits and automated version bumps. The bundled script filters the most common noise automatically (version bump commits via `--invert-grep`, merge commits via `--no-merges`). Some noise may still slip through — NX upgrades, CI config, non-standard version bumps, reverts that cancel out.
 
-- **Version bump commits** (`Bump version from "X" to "Y" [skip ci]`) are filtered out automatically. These touch every package.json but contain no meaningful code changes.
-- **Merge commits** are excluded via `--no-merges`. Only the actual code-change commits from feature branches are shown.
+**Always judge from the actual diff.** Storybook does not consistently follow conventional commits, so commit messages are unreliable for triage decisions.
 
-However, some noise may still slip through:
-- Internal build/tooling changes (NX upgrades, CI config) that touch monitored paths
-- Commits that only change `package.json` version fields without the standard "Bump version" prefix
-- Reverts that cancel out earlier changes
+## Sync Priority Criteria
+
+**High** — sync soon:
+- Bug fixes in logic that was adapted into storybook-rsbuild
+- Security patches
+- API / type / interface changes (options, preset signatures, exports)
+- Breaking changes or deprecations
+
+**Medium** — review and decide:
+- New features that could benefit storybook-rsbuild users
+- Significant refactoring of adapted code patterns
+- Performance improvements in shared logic
+
+**Low** — nice to know:
+- Minor code quality improvements
+- Added error handling or edge-case guards
+- Test changes that reveal expected behavioral contracts
 
-**Critical**: Do not rely on commit messages or file lists for triage decisions. Storybook does not consistently follow conventional commits — subjects like "Build: ...", "Fix ...", "Upgrade ...", or freeform descriptions are common. The actual diff is the only reliable source of truth for judging whether a change needs to be synced. Always read the diff.
+**Skip**:
+- Webpack/Vite internal plumbing with no Rsbuild parallel (e.g. webpack plugin hooks, Vite-specific HMR wiring, Vite module graph internals)
+- Documentation-only changes
+- CI/tooling changes internal to the Storybook repo
+- Changes to `storybook/internal/*` APIs (these arrive via the `storybook` npm dependency, not by manual sync)
+- Pure test file additions with no behavioral insight
+- Build system changes (NX, workspace config, import rewriting) that are specific to the Storybook monorepo structure
 
 ## Workflow
 
 ### 1. Preparation
 
-Generate the report filename first (anchored to system clock):
+Generate the report filename (anchored to system clock):
 ```bash
 REPORT_NAME=$(bash <skill-dir>/scripts/fetch_upstream.sh --report-name)
 ```
 
 Determine the commit range from the user's request:
-- **Relative days**: "past 20 days", "last 30 days"
-- **Absolute date range**: "since 2025-12-01", "Dec 1 to Dec 20"
-- **Version tags**: "between v8.4.0 and v8.5.0", "since v8.4.0"
-- If unspecified, default to the last 30 days.
+- **Relative days**: "past 20 days", "last 30 days" → use `--days N`
+- **Absolute date range**: "since 2025-12-01", "Dec 1 to Dec 20" → use `--since` / `--until`
+- **Version tags**: "between v8.4.0 and v8.5.0" → use `--from` / `--to`
+- If unspecified, default to `--days 30`.
 
 **Important**: For relative date ranges, always use `--days N`. The script reads the system clock to compute exact dates, avoiding date miscalculation.
 
-### 2. Get commit summary and plan analysis
+### 2. Get commit summary and decide strategy
 
-Fetch the commit list with diff line counts (lightweight — no full diffs):
+Fetch the commit list with diff line counts:
 
 ```bash
-bash <skill-dir>/scripts/fetch_upstream.sh --summary --days 30
+bash <skill-dir>/scripts/fetch_upstream.sh --summary --days <N>
 ```
 
 Output: `HASH|DATE|AUTHOR|SUBJECT|LINES_ADDED+LINES_DELETED` (one per line, oldest first).
 
-Based on the commit count, decide the analysis strategy:
-
-- **8 or fewer commits**: Analyze directly using `--diff-all` (no subagents needed, proceed to step 3a).
-- **More than 8 commits**: Use subagents for parallel analysis (proceed to step 3b).
+Based on the commit count:
+- **≤ 8 commits** → step 3a (direct analysis)
+- **> 8 commits** → step 3b (subagent analysis)
 
-### 3a. Direct analysis (small range)
+### 3a. Direct analysis (≤ 8 commits)
 
 ```bash
-bash <skill-dir>/scripts/fetch_upstream.sh --diff-all --days 30
+bash <skill-dir>/scripts/fetch_upstream.sh --diff-all --days <N>
 ```
 
-Read through each commit's diff, compare with local code, and classify. Then go to step 4.
+For each commit in the output:
+1. **Read the diff** — this is the ground truth. Never skip a commit based on its message or file list alone.
+2. **Read the corresponding local source file** using the package mapping table above.
+3. **Classify** using the sync priority criteria above.
+4. **Check for revert chains** — if a commit and its revert both appear, check if the net effect is zero. If so, classify both as skip.
+
+Then proceed to step 4.
 
-### 3b. Batched analysis with subagents (large range)
+### 3b. Subagent analysis (> 8 commits)
 
-**Plan batches** using the summary output:
+**Plan batches** using the `--summary` output:
 
 1. Sum the total lines changed across all commits.
 2. Target 3–5 subagents. Calculate: `target_lines_per_batch = total_lines / batch_count`.
@@ -142,8 +165,6 @@ KEY_FILES: <comma-separated list of relevant changed files>
 
 Save to `$REPORT_NAME` in the project root.
 
-**Report template:**
-
 ```markdown
 # Storybook Upstream Sync Report
 
@@ -182,28 +203,14 @@ Save to `$REPORT_NAME` in the project root.
 
 Commits within each priority section should be in chronological order (oldest first).
 
-## Sync Priority Criteria
+### 5. Offer to create an issue
 
-**High** — sync soon:
-- Bug fixes in logic that was adapted into storybook-rsbuild
-- Security patches
-- API / type / interface changes (options, preset signatures, exports)
-- Breaking changes or deprecations
+After writing the report, ask the user if they want to publish it as a GitHub issue in this repository. If yes, create the issue using `gh`:
 
-**Medium** — review and decide:
-- New features that could benefit storybook-rsbuild users
-- Significant refactoring of adapted code patterns
-- Performance improvements in shared logic
-
-**Low** — nice to know:
-- Minor code quality improvements
-- Added error handling or edge-case guards
-- Test changes that reveal expected behavioral contracts
+```bash
+gh issue create --title "<TITLE>" --body-file "$REPORT_NAME"
+```
 
-**Skip**:
-- Webpack/Vite internal plumbing with no Rsbuild parallel (e.g. webpack plugin hooks, Vite-specific HMR wiring, Vite module graph internals)
-- Documentation-only changes
-- CI/tooling changes internal to the Storybook repo
-- Changes to `storybook/internal/*` APIs (these arrive via the `storybook` npm dependency, not by manual sync)
-- Pure test file additions with no behavioral insight
-- Build system changes (NX, workspace config, import rewriting) that are specific to the Storybook monorepo structure
+**Title format**: `Storybook Sync: <range>` — where `<range>` matches the range used in the report. Examples:
+- Date range: `Storybook Sync: 2026-03-12 – 2026-04-11`
+- Version range: `Storybook Sync: v8.4.0 – v8.5.0`

…k-sync-checker/scripts/fetch_upstream.sh …storybook-sync/scripts/fetch_upstream.sh.claude/skills/storybook-sync-checker/scripts/fetch_upstream.sh renamed to .agents/skills/storybook-sync/scripts/fetch_upstream.sh .claude/skills/storybook-sync-checker/scripts/fetch_upstream.sh renamed to .agents/skills/storybook-sync/scripts/fetch_upstream.sh

@@ -0,0 +1 @@
+../.agents/skills