القائمة
Use when reviewing code changes in the Stacks project — two-pass code review with critical issue detection, test coverage audit, and auto-fix workflow. Invoke with /stacks-review.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use for headless browser QA on Stacks applications — navigation, screenshots, responsive testing, console/network monitoring, and accessibility snapshots. Dependency-free: drives a system browser over the Chrome DevTools Protocol using only Bun (no Playwright/Puppeteer). Invoke with /stacks-browse.
Use when styling components in a Stacks application — utility-first CSS classes, theming, responsive design, variants, custom rules, or CSS generation. Crosswind is the CSS utility engine powering Stacks' Crosswind config.
Use when working with UI in a Stacks application — components, composables, reactivity (refs/watch/computed), Craft native components, Crosswind CSS, Crosswind utility framework, accessibility, or the STX templating engine. Covers @stacksjs/ui, @stacksjs/stx, and related UI tooling.
Use when building, modifying, or debugging API endpoints in a Stacks application — defining routes, handling requests, API middleware, working with the API server, HTTP client (fetcher), API resources, or OpenAPI generation. Covers both @stacksjs/api utilities and the stacks-api server implementation.
Use when working with routing in a Stacks application — defining routes, HTTP methods, route groups, middleware, named routes, URL generation, request enhancement (Laravel-style input/query/file helpers), response helpers, error responses, route model binding, or rate limiting. Covers @stacksjs/router, routes/, and app/Routes.ts.
Use when defining or organizing route files in a Stacks application — creating route files in routes/, registering them in app/Routes.ts, using route prefixes and middleware groups, or the default API routes structure. For the router API itself (request helpers, response helpers, middleware classes), see stacks-router.
| name | stacks-review |
| description | Use when reviewing code changes in the Stacks project — two-pass code review with critical issue detection, test coverage audit, and auto-fix workflow. Invoke with /stacks-review. |
| license | MIT |
| compatibility | Bun >= 1.3.0, TypeScript |
| allowed-tools | Read Edit Write Bash Grep Glob |
You are performing a structured two-pass code review for the Stacks framework. Be direct, specific, and opinionated. Every finding must reference a specific file and line number.
git diff --cached). If nothing staged, review unstaged (git diff)Read changed files in full to understand context around the changes.
Scan for issues that must be fixed before merge. Only flag with confidence 8/10+:
config/services.ts)await on async callsdb.close())factory for seeder)config/*.ts files@stacksjs/* package exportsFor each critical finding:
🔴 CRITICAL: [title]
File: [path]:[line]
Issue: [specific description]
Impact: [what can go wrong]
Fix: [concrete fix, not "consider doing X"]
Scan for non-blocking issues:
bunx --bun pickier compliance (don't flag what pickier catches)any, prefer discriminated unions, use satisfies)gitlint standards)For each:
🟡 INFO: [title]
File: [path]:[line]
Note: [observation]
Suggestion: [improvement]
bun test files)## Test Coverage
| Changed Function | Test File | Covered? |
|-----------------|-----------|----------|
| [function] | [test file or "none"] | ✅ / ❌ |
Missing coverage:
- [untested path or edge case]
After presenting findings, ask:
"Want me to fix the mechanical issues? (formatting, imports, simple type fixes)"
If yes, fix ONLY mechanical issues. After fixing, run bunx --bun pickier . --fix.
Do NOT auto-fix: architectural decisions, logic changes, anything with multiple valid approaches.
# Code Review: [brief description]
## Pass 1: Critical Issues
[findings or "No critical issues found."]
## Pass 2: Informational
[findings]
## Test Coverage
[table]
## Summary
- Critical: [count]
- Informational: [count]
- Test gaps: [count]
pickier would catchstorage/framework/types/ auto-generated typescore/ might affect 15+ downstream packagesReview complete. Run
/stacks-browseto QA in the browser, or/stacks-retroto reflect on this session.