메뉴
Pake project adapter for Waza check/code-review. Use for TypeScript CLI, Rust/Tauri, release artifact, and CI review.
Package any website into a lightweight desktop app using Pake (Tauri/Rust). Use when the user wants to: wrap a URL as a native app, build a desktop app from a website, use Pake CLI to package a page, set up proxy for a packaged app, customize app icons or bundle IDs, or mentions 'pake', 'tauri package', 'website to app', 'wrap site'. Also trigger when the user asks about Pake CLI options, proxy configuration for packaged apps, or icon handling.
GitHub issue, PR, and release operations via gh CLI. Not for code review or release builds.
Prepare, validate, and publish a Pake release. Not for version bumps without release intent.
| name | code-review |
| description | Pake project adapter for Waza check/code-review. Use for TypeScript CLI, Rust/Tauri, release artifact, and CI review. |
| version | 1.2.0 |
| allowed-tools | ["Bash","Read","Grep","Glob"] |
| disable-model-invocation | true |
Use Waza /check for the generic review method. This adapter adds Pake-specific commands, hard stops, and artifact rules.
bin/ rebuild and commit dist/cli.js with pnpm run cli:build.package.json name/version/repository/bin/scripts/exports) rebuild and commit dist/cli.js.package.json, src-tauri/Cargo.toml, src-tauri/Cargo.lock, and src-tauri/tauri.conf.json in sync..github/workflows/npm-publish.yml, id-token: write, canonical git+https://github.com/tw93/Pake.git, and scripts/check-release-version.mjs.tauriConf: any or other untyped config objects; use PakeTauriConfig.panic! or .unwrap() on config, CLI, or event paths.catch {} blocks surface the real error through logger.warn.bin/utils/ or bin/helpers/ has a matching tests/unit/<basename>.test.ts.# Get PR diff
gh pr diff
# Format check
pnpm run format:check
# Run unit tests (fast, sub-second)
npx vitest run
# Full suite without the slow real build
pnpm test -- --no-build
# Build CLI and catch TypeScript errors
pnpm run cli:build
Follow Waza /check: findings first, ordered by severity, with tight file/line references. Keep summaries brief.