القائمة
pcraft release & versioning conventions — single SemVer across npm, GitHub release, and Docker. Use when cutting a release, debugging release artifacts, or answering questions about version channels.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
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.
Review changed code for quality, security, and architecture compliance. Use after implementing features or before opening PRs.
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.
استنادا إلى تصنيف SOC المهني
| name | release |
| description | pcraft release & versioning conventions — single SemVer across npm, GitHub release, and Docker. Use when cutting a release, debugging release artifacts, or answering questions about version channels. |
pcraft uses a single SemVer X.Y.Z shared across all distribution channels.
apps/cli/package.json version → X.Y.Zpcraft@X.Y.Z@beilin/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)vX.Y.Z with platform tarballs pcraft-{platform}.tar.gz + .sha256ghcr.io/avatarganymede/pcraft:{version,tag,latest,universal}Entirely in CI via .github/workflows/release.yml, triggered by a maintainer from the GitHub Actions UI:
bump (patch/minor/major) → optional dry_run.prepare job bumps version + regenerates CHANGELOG, opens release PR, squash-merges, tags vX.Y.Z.build-web + 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 @beilin/runtime-* packages + main pcraft package to npmjs.There is no local release script — the entire flow runs in GHA.
The npm shim (apps/cli/bin/native-shim.js) locates the bundled runtime via:
PCRAFT_BUNDLE_DIR env var (used by tests and explicit overrides).@beilin/runtime-{platform} npm package via require.resolve().The native Go launcher (apps/backend/cmd/pcraft) is spawned by the npm shim for run / start / service commands.
Before the first release, configure Trusted Publishers on npmjs.com for all 6 packages:
pcraft@beilin/runtime-linux-x64, @beilin/runtime-linux-arm64@beilin/runtime-darwin-x64, @beilin/runtime-darwin-arm64@beilin/runtime-win32-x64Each package needs this GitHub Actions workflow (release.yml) registered as its trusted publisher.