canary
無料Finds or publishes a pkg.pr.new canary release for a Storybook branch. Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually.
日本語の概要は準備中です。原文の説明を表示しています。
Recomputes Storybook browser support floors from Plausible /docs usage, writes pinned versions, and opens a PR. Use only when a human explicitly applies this skill.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Need PLAUSIBLE_API_KEY in the environment. How the operator supplies the key is up to them. Do not print the key.
POST https://plausible.io/api/v2/query
site_id: storybook.js.orgdate_range: "30d"filters: [["contains", "event:page", ["/docs"]]]dimensions: ["visit:browser", "visit:browser_version"]metrics: ["visitors", "percentage"]include: { "total_rows": true }Save the request, resolved date range, retrieval time, and complete response. Fetch all pages before rolling versions. Use the same fixed date range for every request in the run.
Plausible's Stats API reference defines percentage as the percentage of total visitors in each category. With the query above, the denominator is all unique visitors matching the /docs page filter during the selected period, across all browsers and versions. It is not the total for one browser or the sum of the returned version rows. In each result row, metrics[0] is visitors and metrics[1] is percentage. Use metrics[1] as the share for an unrolled category. The 0.5% cutoff means percentage >= 0.5, not 0.005.
Also query metrics: ["visitors"] with no dimensions and the same site, date range, and page filter to record the denominator. Do not add browser filters to this denominator query.
/docs visitors × 100. For a rolled version containing multiple raw versions, query metrics: ["visitors"] with no dimensions, the same site/date/page filter, and additional is filters for that browser and its matching raw versions. Divide this unique-visitor count by the recorded denominator and multiply by 100 to get the rolled share. Do not sum unique-visitor counts or percentages across raw versions; a visitor can appear in more than one row.Companions: android / and_chr = Chrome floor. ios_saf = Safari floor. Leave Node unchanged.
The heuristic does not define a numerical boundary between the current cluster and an older island. Do not infer that boundary silently or write new floors without explicit operator approval.
Present the saved query evidence and a table for each browser containing:
/docs visitors.Record the operator's approval, identity, date, and selected versions with the evidence in the PR. The floor is the oldest qualifying version in that approved cluster. If the operator disputes the boundary or the evidence cannot distinguish clusters, stop and ask the Technical Architect to resolve the selection semantics. Do not change the policy to break a tie. Reuse of the saved evidence and approval must yield the same floors.
Pin explicit versions (do not leave a live query):
code/core/src/shared/constants/environments-support.ts — BROWSER_TARGETS (chromeN, edgeN, firefoxN, safariN.N, iosN.N; Opera only if kept)code/package.json — browserslistdocs/get-started/install.mdx — public list and older-browser fallback guidance, scoped to the same Storybook versions as MIGRATION.md; preserve the preview-only limitationsMIGRATION.md — next major From version X.x to Y.0.0 section. Create that section at the top if it does not exist.If browserslist cannot resolve the new pins, bump caniuse-lite (root resolutions + lockfile). The repo has a 7-day npm age gate.
Branch from origin/next. Open a PR that targets next and follows .github/PULL_REQUEST_TEMPLATE.md. Add labels ci:normal, qa:skip, and BREAKING CHANGE.
In What I did, keep it short: before → after versions, and the share of /docs visitors for each chosen floor.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Finds or publishes a pkg.pr.new canary release for a Storybook branch. Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually.
日本語の概要は準備中です。原文の説明を表示しています。
Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Checks out a PR (including fork PRs), fixes all linting and TypeScript errors, then pushes the changes back. Use when asked to fix lint, types, or TS errors on a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Label GitHub issues and PRs found during QA testing. Use when organizing QA findings with proper labels.
日本語の概要は準備中です。原文の説明を表示しています。
Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.
日本語の概要は準備中です。原文の説明を表示しています。
Use when adding Storybook to a project that does not have Storybook configured yet.
日本語の概要は準備中です。原文の説明を表示しています。