القائمة
Prepare publishable SDK package changes for push and PR in better-webhook. Use when changes under packages/* need a Changeset, SDK docs or README updates, full verification, and a release-ready PR summary before code is pushed to GitHub.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Create git commits using Conventional Commits. Use when the user asks to commit code, prepare a commit, write a commit message, or standardize commit history with conventional commit types, scopes, breaking-change markers, and safe git workflow checks.
Fetch dependency source code so agents can inspect real implementations, tests, and version-specific behavior. Use when docs or types are insufficient, when debugging library internals, or when tasks require source-backed evidence. Triggers include "fetch source for", "read the source of", "how does X work internally", "get the implementation of", and "opensrc path".
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
Break a plan, spec, or PRD into independently-grabbable local markdown issues under `.workflows/` using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tasks, or break down work into issues.
Turn the current conversation context into a local markdown PRD under `.workflows/prd/`. Use when user wants to create a PRD from the current context.
| name | sdk-release |
| description | Prepare publishable SDK package changes for push and PR in better-webhook. Use when changes under packages/* need a Changeset, SDK docs or README updates, full verification, and a release-ready PR summary before code is pushed to GitHub. |
Use this skill when a change touches one or more publishable SDK packages under packages/*.
Get an SDK change release-ready before pushing a branch or opening a PR. Do not publish, version packages, or create tags on a feature branch unless the user explicitly asks for the real release.
packages/* changed and which of them are publishable (package.json is not private: true).apps/examples/* as non-release artifacts; they are intentionally ignored by Changesets.major: breaking API or runtime behaviorminor: backward-compatible featurepatch: bug fix, compatible behavior change, compatible type improvement, or compatible docs fix tied to shipped behaviordevbox run -- pnpm changeset.package.json versions or edit CHANGELOG.md; Changesets owns that.README.md.apps/docs/content when SDK behavior, APIs, setup, or release expectations changed.devbox run -- pnpm run format:writedevbox run -- pnpm run format:checkdevbox run -- pnpm run lintdevbox run -- pnpm run check-typesdevbox run -- pnpm run testdevbox run -- pnpm run buildmain:
main with npm trusted publishing via OIDC and provenance attestationschangeset version, changeset publish, or create tags as part of normal pre-PR prep.