Code Review
Testing & Qualitycode-reviewCode Review is an Agent Skill for testing & quality published in the tw93/Pake repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Pake project adapter for Waza check/code-review. Use for TypeScript CLI, Rust/Tauri, release artifact, and CI review.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/tw93/Pake/blob/HEAD/.agents/skills/code-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/code-review, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Pake Code Review Adapter
Use Waza /check for the generic review method. This adapter adds Pake-specific commands, hard stops, and artifact rules.
Pake-Specific Hard Stops
- Changes under
bin/rebuild and commitdist/cli.jswithpnpm run cli:build. - Changes to package metadata embedded by Rollup (
package.jsonname/version/repository/bin/scripts/exports) rebuild and commitdist/cli.js. - Release version bumps keep
package.json,src-tauri/Cargo.toml,src-tauri/Cargo.lock, andsrc-tauri/tauri.conf.jsonin sync. - npm release workflow changes preserve Trusted Publishing:
.github/workflows/npm-publish.yml,id-token: write, canonicalgit+https://github.com/tw93/Pake.git, andscripts/check-release-version.mjs. - Release/status changes keep npm registry, GitHub Release/assets, workflow run state, and issue closeout as separate truth surfaces.
-
workflow_dispatchrelease logic does not infer the release tag fromheadBranch, run title, or compare UI; use an explicit tag/ref and verify the packagegitHead. - Any new user-visible CLI flag, alias, or help variant carries an explicit justification for why existing options or defaults cannot cover it (maintainer sign-off, not inferred).
- No new
tauriConf: anyor other untyped config objects; usePakeTauriConfig. - No user-reachable
panic!or.unwrap()on config, CLI, or event paths. - Silent
catch {}blocks surface the real error throughlogger.warn. - New helper in
bin/utils/orbin/helpers/has a matchingtests/unit/<basename>.test.ts. - Binary parsers have a round-trip test, not only builder assertions.
- Linux WebKit/AppImage runtime flag changes keep the default conservative, add or update tests for the decision logic, and update
docs/faq*.mdwhen users need a fallback command. - macOS
--new-windowor auth URL changes include targeted tests for popup/auth routing insrc-tauri/src/inject/event.js.
Quick Review Commands
# 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
Review Output Format
Follow Waza /check: findings first, ordered by severity, with tight file/line references. Keep summaries brief.