القائمة
Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
Diagnose Kandev bugs, running-instance issues, UI/browser failures, and runtime behavior. Use when the user reports unexpected behavior, asks to investigate, asks to add logs/instrumentation, or when a fix needs root-cause evidence before implementing. Triage first, gather evidence safely, then hand off to /fix or /tdd for code changes.
Write and run web E2E tests (Playwright) using TDD — locations, patterns, commands, and debugging.
Ensures UI feature work ships with desktop and mobile parity, responsive behavior, and mobile Playwright E2E coverage. Use when implementing, planning, reviewing, or testing any new feature, page, component, workflow, form, dialog, sidebar, navigation, dashboard, or visual UI change; if work touches frontend or user-facing UI, this skill must run even when user mentions only desktop or says "new feature".
Create a committed implementation plan from a feature spec. Explores the codebase, designs the approach, and produces docs/plans/<feature>/plan.md plus individual task files. Use after writing a spec and before implementing.
Wait for CI checks and automated reviews (CodeRabbit, Greptile, Claude, OpenCode, cubic) on a PR, fix failures and address comments, then push.
| name | release |
| description | Kandev release & versioning conventions — single SemVer across npm, Homebrew, GitHub release. Use when cutting a release, debugging release artifacts, or answering questions about version channels. |
Kandev uses a single SemVer X.Y.Z shared across all distribution channels.
apps/cli/package.json version → X.Y.Zkandev@X.Y.Z@kdlbs/runtime-{platform}@X.Y.Z (5 platforms; declared as optionalDependencies in main package)vX.Y.Z (three-part; legacy vM.m tags normalize to M.m.0)kdlbs/homebrew-kandev Formula/kandev.rb version "X.Y.Z"vX.Y.Z with platform tarballs kandev-{platform}.tar.gz + .sha256npm and Homebrew are sibling channels, not chained. Both consume the same GitHub release artifacts; neither depends on the other.
Entirely in CI via .github/workflows/release.yml, triggered by a maintainer from the GitHub Actions UI:
bump (patch/minor/major) → optional dry_run or desktop_validation_only.prepare job bumps version + regenerates CHANGELOG, opens release PR, squash-merges, tags vX.Y.Z.build-web + build-cli + build-bundles (5 platforms) build the release artifacts.publish-release creates the GitHub release with platform tarballs + sha256 + auto-generated notes.publish-npm publishes 5 @kdlbs/runtime-* packages + main kandev package to npmjs.update-homebrew-tap pushes updated Formula/kandev.rb to kdlbs/homebrew-kandev via SSH deploy key.There is no local release script — the entire flow runs in GHA.
Desktop signing is automatic. Complete macOS/Windows signing and notarization secrets produce signed artifacts; missing or incomplete signing inputs produce unsigned desktop artifacts and the GitHub release notes get an unsigned-artifact warning. desktop_validation_only=true builds artifacts from the current workflow ref for maintainer inspection and skips the release PR, tag, GitHub release, npm publish, Homebrew update, and public container tags.
In apps/cli/src/runtime.ts, the CLI locates its bundled runtime via:
KANDEV_BUNDLE_DIR env var (set by Homebrew wrapper, used by tests).@kdlbs/runtime-{platform} npm package via require.resolve().--runtime-version <tag> cache fallback (debug only — downloads from GitHub).