菜单
Plan and review Waitkit library architecture, package boundaries, public exports, TypeScript/tsup output, package metadata, and release impact. Use for API design, package refactors, new package planning, and architecture decisions.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/junjuny0227/waitkit --skill library-architecture命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Collect Waitkit GitHub PR review comments, assess each comment against project rules, apply valid fixes when safe, optionally commit and push fixes, and post Korean replies with gh api. Use only when the user explicitly asks to address PR review comments or reply to review comments.
Review Waitkit changed files using .claude/rules, package boundaries, public API contracts, core behavior, tests, docs, Changesets, release workflow, security basics, and validation results.
Create actual Waitkit Git commits by inspecting changed files, splitting logical units, staging the right files, and running git commit with project Conventional Commit messages. Use only when the user explicitly asks to commit.
基于 SOC 职业分类
正在显示 SKILL.md
| name | library-architecture |
| description | Plan and review Waitkit library architecture, package boundaries, public exports, TypeScript/tsup output, package metadata, and release impact. Use for API design, package refactors, new package planning, and architecture decisions. |
Use this skill to keep Waitkit changes small, framework-agnostic, and safe for published packages.
packages/core: current publishable package.packages/core/src/index.ts: public API surface.packages/core/src/*.ts: internal implementation modules.packages/core/tests: Vitest coverage.packages/eslint-config and packages/typescript-config: shared tooling.@waitkit/core independent from React, MSW, and CLI concerns.exports, README examples, and tests as one
contract.For non-trivial changes, produce a short plan with API impact, package boundary impact, files likely to change, tests, and release notes or changeset needs.