القائمة
Use for git-based session retrospectives — session detection, commit categorization, focus scores, streak counting, and behavioral observations. Invoke with /stacks-retro.
التثبيت باستخدام 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-retro |
| description | Use for git-based session retrospectives — session detection, commit categorization, focus scores, streak counting, and behavioral observations. Invoke with /stacks-retro. |
| license | MIT |
| compatibility | Bun >= 1.3.0, TypeScript |
| allowed-tools | Read Edit Write Bash Grep Glob |
Generate a retrospective analysis of recent development work based on git history.
Detect sessions using a 45-minute gap threshold between commits.
git log --all --format="%H|%ai|%an|%s" --since="7 days ago"
Adjust --since if user specifies a range ("today", "this week", etc.).
| Category | Indicators | Icon |
|---|---|---|
| Feature | feat:, new files, new exports | 🟢 |
| Fix | fix:, corrective changes | 🔴 |
| Refactor | refactor:, structural changes | 🔵 |
| Test | test:, test file changes | 🟡 |
| Docs | docs:, README changes | 📝 |
| Chore | chore:, deps, config, CI | ⚙️ |
| Style | style:, formatting, lint | 🎨 |
Parse gitlint-style conventional commit prefixes. Stacks uses these scopes: core, auth, database, router, buddy, ui, build, etc.
focus_score = (commits_in_primary_area / total_commits) × 100
Primary area = most-touched storage/framework/core/*/ package or top-level directory.
### Session [N]: [start] → [end] ([duration])
**Focus**: [score]/100 — [assessment]
**Primary area**: [package/directory]
**Commits**: [count]
| Time | Category | Message | Files |
|------|----------|---------|-------|
**Observation**: [one behavioral insight]
git log --all --format="%ad" --date=short | sort -u
## Streaks
🔥 Current streak: [N] days
📈 Longest streak: [N] days ([range])
📅 Active days: [N] / [total]
| Contributor | Commits | Primary Focus | Top Category | Avg Focus |
|-------------|---------|---------------|--------------|-----------|
2-4 observations backed by data:
# Retrospective: [date range]
## Overview
- **Period**: [range]
- **Sessions**: [count]
- **Total commits**: [count]
## Category Breakdown
[icons and counts]
## Sessions
[session details]
## Streaks
[streak data]
## Observations
[behavioral insights]
## Suggested Focus for Next Session
[one specific suggestion]