菜单
Determine the correct `@since` JSDoc version for new public API in @toolbox-web libraries, and bulk-refresh existing tags. Use whenever you add a public type, interface, method, property, exported constant, or event detail and need its `@since` value — instead of guessing.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Prepare a @toolbox-web library for release AND drive release-please versioning. Covers the pre-release checklist (lint, test, build, bundle size, CHANGELOG, docs) PLUS release-please version operations — graduating a prerelease to GA (rc → stable), switching the prerelease identifier (beta → rc), and the per-package path-scoped Release-As bootstrap commits. Use when cutting a release, promoting a prerelease line to stable, or whenever release-please proposes the wrong version (e.g. an rc/patch bump when you expect the clean GA version like 3.0.0).
Run deterministic codebase-intelligence analysis with fallow. Covers health scoring (complexity/CRAP/refactor targets), dead code, duplication, dependency hygiene, and PR-scoped audit. Use before opening a PR, as part of `/qa`, or to identify refactoring opportunities in a file or plugin. Produces machine-actionable JSON findings that can be fed directly into `qa-apply-findings`.
Add a new feature OR backport a bugfix consistently across the Angular, React, and Vue adapter libraries for @toolbox-web/grid. Use whenever you touch one adapter, to confirm the other two need the same change and to keep full parity.
Create a new framework adapter library for @toolbox-web/grid, with a matching demo app. Covers library scaffolding, adapter implementation, demo setup, workspace wiring, and e2e parity testing.
Author, restructure, or update documentation for the Astro/Starlight docs site. Covers ADDING a new docs page or route (MDX + sidebar registration in astro.config.mjs + llms.txt/llms-full.txt inclusion), which prose/MDX and API-reference docs to check after a code change, how to write them, the `<Audience>` and `llmsFull` curation knobs, and regenerating typedoc API docs. Use whenever you create, move, rename, or edit any file under apps/docs/, or after any feature, fix, or refactor that touches user-visible behaviour. (For building a new interactive demo component, use the astro-demo skill instead.)
Read, reply to, and resolve review-comment threads on a GitHub pull request using the gh CLI. Use whenever you need to triage PR feedback (fetch all unresolved review threads as structured JSON, post inline replies on specific threads, and mark threads resolved) instead of hand-writing a one-off gh/GraphQL script each time. Prefer this over the generic address-pr-comments skill for bulk thread triage and programmatic gh/GraphQL access.
| name | since-tag |
| description | Determine the correct `@since` JSDoc version for new public API in @toolbox-web libraries, and bulk-refresh existing tags. Use whenever you add a public type, interface, method, property, exported constant, or event detail and need its `@since` value — instead of guessing. |
@since Tag Versioning@since tags appear verbatim in the TypeDoc API reference and the docs site, so a wrong value misleads users about which release introduced an API. Never copy a @since from a neighboring symbol and never guess — resolve it deterministically with the script below.
All scripts for this concern live in this skill folder (nothing else in the repo calls them):
| File | Purpose |
|---|---|
resolve-since.mjs | Compute the @since version for ONE new symbol you're adding now |
build-since-map.ts | Bulk: scan git history → since-map.json (first release tag per export) |
apply-since-tags.ts | Bulk: write @since tags from since-map.json into source |
since-map.json | Generated map consumed by apply-since-tags.ts |
Run the resolver with the affected library and your change's commit type. It prints the version to stdout and a one-line explanation to stderr.
bun .github/skills/since-tag/resolve-since.mjs <lib> <bump>
<lib>: grid | grid-angular | grid-react | grid-vue (default grid)<bump>: feat | fix | perf | refactor | breaking (or explicit major/minor/patch; default feat)--no-fetch: skip the best-effort fetch of the release-please branch (use offline or to keep it fast when the remote-tracking ref is already local)# Adding a new feature to the core grid:
bun .github/skills/since-tag/resolve-since.mjs grid feat # → 2.16.0
# Capture for scripting:
SINCE=$(bun .github/skills/since-tag/resolve-since.mjs grid-react fix)
Then stamp the printed value on the declaration:
/** @since 2.16.0 */
export interface NewThing { … }
lastReleased = .release-please-manifest.json["libs/<lib>"] (authoritative)
staged = version in libs/<lib>/package.json on
origin/release-please--branches--main, else lastReleased
prCandidate = lastReleased bumped by <bump>'s tier
result = semver max(staged, prCandidate)
A PR can only raise release-please's staged tier, never lower it, so the max is always correct:
| Staged (queued) | Your PR | Result |
|---|---|---|
2.16.0 (feat) | fix | 2.16.0 — staged wins |
2.15.2 (fix) | feat | 2.16.0 — your PR upgrades tier |
2.16.0 (feat) | breaking | 3.0.0 — your PR upgrades to major |
| none | feat | 2.16.0 — lastReleased + minor |
Tier mapping mirrors
release-please-config.json:feat:→ minor;fix:/perf:/refactor:→ patch;feat!:/BREAKING CHANGE→ major. When genuinely unsure whether your change is a feat or a fix, ask the user before stamping.
Use after a release cycle to back-fill / correct @since across all public exports. apply-since-tags.ts is idempotent (skips declarations that already have any @since); --force rewrites stale tags to match the regenerated map.
bun .github/skills/since-tag/build-since-map.ts
bun .github/skills/since-tag/apply-since-tags.ts # or --force
# Regenerate API docs so the Since pills update:
bun nx typedoc grid && bun nx typedoc grid-angular && bun nx typedoc grid-react && bun nx typedoc grid-vue
build-since-map.tsMUST enumerate every TypeDoc entry point (gridsrc/public.ts+ everylibs/grid/src/lib/plugins/*/index.ts, plus each adapter's single entry). Missing an entry silently drops those symbols from the map and the docs render no Since pill.