بنقرة واحدة
check
Run local quality checks (typecheck, lint, format, build, tests). Quick check during development.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Run local quality checks (typecheck, lint, format, build, tests). Quick check during development.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Proactively hunt for cdk-local bugs by synthesizing real CDK apps that exercise common-but-untested AWS resources, configs, and CloudFormation notations, then RUNNING them locally in Docker (invoke / start-api / run-task / start-service / start-alb / start-cloudfront / invoke-agentcore / studio) and catching local-execution failures + divergences from deployed behavior. Use for a periodic "find latent bugs" sweep, not for verifying a specific change.
Work through already-filed GitHub issues (typically the bug-hunt's output) end to end — triage safely, pick a few FILE-DISJOINT issues to fix in parallel, claim each on the issue before starting (collision-safe with other agents), verify, then carry each through merge (via /merge-pr) → pull → worktree cleanup. Use when asked to "handle/address filed issues", not to hunt for new bugs (that is /hunt-bugs).
Squash-merge a PR and fully clean up the feature worktree + local branch, without tripping the side-worktree `'main' is already used by worktree` fatal and without bypassing the merge-time gates.
Detect and delete leftovers from interrupted cdk-local runs — Docker containers / networks, AND orphaned vitest forks worker processes that failed to terminate (issue
Triggers when a PR adds a new subcommand factory, CLI option, public helper, or behavior change to cdk-local that cdkd (host CLI) may need to inherit. Walks the diff and pins each category to "exported via internal.ts / inside add<Cmd>SpecificOptions / cdkd notified" — sets the cdkd-parity marker so gh pr create can fire.
Check if documentation (README.md, .claude/CLAUDE.md) is up to date with recent code changes. Use when code has been modified and docs may be stale.
| name | check |
| description | Run local quality checks (typecheck, lint, format, build, tests). Quick check during development. |
Run all local quality checks. Use during development to verify the current state quickly.
Run these sequentially and report results:
vp run check — typecheck + lint + format check (the unified task wired in vite.config.ts).vp run build — produces dist/cli.js and dist/index.js.vp run test — vitest unit tests.vp run verify is the convenience alias that runs all three; either path is fine.
Report as a table:
| Check | Result |
|---|---|
typecheck + lint + format (vp run check) | pass/fail |
| build | pass/fail |
| tests (N files, M tests) | pass/fail |
If all pass, confirm "All checks passed." If any fail, show the error output and STOP — do not write the commit-gate marker.
After all three checks pass, record a marker so the check gate is fresh. The marker is managed by markgate and captures the current working tree state; any subsequent edits invalidate it and require re-running /check.
Run this from the repo root (cdk-local pins markgate via mise, so use mise exec to avoid PATH issues when shims aren't active):
mise exec -- markgate set check
Skip this step if any check failed — a stale or missing marker correctly forces re-running /check after fixing the failure.