Enforce non-breaking API rules and validate docs, lint, tsc, tests, and npm packaging for retikz release candidates.
npx skills add https://github.com/Pionpill/retikz --skill flow-rc
Please help me install this Agent Skill. Skill: flow-rc Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/flow-rc Command: npx skills add https://github.com/Pionpill/retikz --skill flow-rc
flow-rc solves the risk of breaking the public API during the npm rc (release candidate) quality-freeze window by enforcing strict non-breaking and no-new-public-capabilities rules while driving the necessary documentation, validation, and release preparation.
next dist-tag installability, tarball hygiene, TypeScript correctness, and external smoke-test viability before publishing rc.0.1.0-rc.N to stable cutoff.Use flow-rc to verify and complete all rc documentation and packaging acceptance for version 0.1.0-rc.N while rejecting any proposed public API or schema-breaking changes.
High-intent search queries and answers about installing and using this skill.
To enforce an API freeze during an npm release candidate window, you must block breaking changes to component names, props, schema fields, and public function signatures while completing required validation. This ensures no new public capabilities are introduced before the stable release.
The release candidate quality freeze process for a TypeScript library coordinates bugfixes, documentation completion, and packaging acceptance while preventing public API modifications. It enforces strict compatibility rules from the rc tag until the final stable version cutoff.
Validate npm packaging and TypeScript correctness before publishing a release candidate by running lint, tsc, and test suites, verifying tarball hygiene, and confirming external install acceptance using the npm next dist-tag strategy.
No, you cannot add new public component props or schema fields when preparing a bugfix for an rc version. The release candidate freeze strictly enforces no-breaking and no-new-public-capabilities rules to maintain API compatibility.
Before publishing a 0.1.0-rc.N release, you must complete bilingual doc site content with zh as the source of truth, migration guides, examples, and release notes. Docs-first delivery ensures all structural and content requirements are finished.
holger1411Run lint, format, TypeScript, and build checks on AstroDeck projects.
yu-iskwPacks the @dbt-tools/web package and smoke-tests its CLI via npx.
tikazyqApply common blog standards to marvinzhang.dev articles.
voidrotGenerate changelogs and release notes from commit history and tags.