genai-demo

Launch and drive the Gatherly app locally (FastAPI backend + Next.js frontend) and verify it renders. Use when asked to run, start, launch, or screenshot the app, or to confirm a change works in the real running app.

Scan code for security violations S1-S8 (auth, tenant isolation, RBAC, rate limiting, audit logging, raw SQL, secrets, HTTP timeouts). Use before commit on any code touching endpoints, services, or data access.

Run the event-readiness checklist against an event. Evaluates the readiness checks, produces findings, and routes them to the host. Use when the user asks to audit, score, or check the readiness of an event.

Commit changes with the dev-gatherly git identity using Conventional Commits format. Use after every atomic step in the REPL loop.

Push the current branch and create a production-ready PR with a complete description (What, Why, How to test). Runs /review-pr first if not already done. Use when implementation is complete.

Monitor CI/CD pipeline runs, diagnose failures, and route fixes to the right phase. Use after pushing a branch or when a pipeline turns red.

Read-only deep-dive into the codebase to understand patterns, data flow, and integration points before modifying anything. Use before any non-trivial change.

Build production-grade UI components and pages using shadcn/ui primitives, Tailwind, dark mode, and i18n. Use whenever creating or modifying user-facing screens or components.

Full REPL loop orchestrator. Runs plan → explore → implement → convene the specialist team (review/audit/test) → acceptance gate → PR for a feature request. Use when the user wants a feature implemented end-to-end.

Scaffold a new FastAPI endpoint with all 5 security guards, repository pattern, service layer, schemas, and tests. Use when adding any HTTP endpoint to the backend.

Add a new readiness check to the Gatherly event-readiness checklist (a ReadinessCheck in InsightsService.get_readiness + tests). Use when the user asks to add a new readiness signal like has_guests, within_capacity, has_location, published, or a custom one.

Send Slack messages, alerts, and notifications. Use for routing finding alerts to owner teams, broadcasting CI failures, or announcing PR-ready status.

Design a feature implementation with acceptance criteria AC-1 through AC-6 before any code is written. Use when starting work on a new feature, bug, or refactor.

Bug-hunt review of an open PR or the current branch's changes. Produces a severity-ranked bug report and a fix plan. Use after /implement and before /create-pr, or on a teammate's PR.

Quality review pass on recently changed code. Looks for duplication, missing reuse of existing utilities, overly clever code, and pattern violations. Use after implementation, before audit.

Classify a bug report, security finding, or feature request. Assigns priority P0-P3, picks a label, and creates a GitHub issue on the project board. Use whenever something needs to enter the backlog.

Autonomous worker that picks up auto-fixable findings from readiness-checklist runs and proposes fixes via PR back to source repos. Use when the user wants to clear the findings backlog hands-free, typically after `/audit-service` has produced findings.

Autonomous worker that picks the highest-priority open GitHub issue, implements it through the full REPL loop, opens a PR, and moves to the next. Use for hands-free backlog clearing.

Write project documentation and publish to Google Drive as Google Docs (or to docs/ as markdown). Use for runbooks, architecture docs, onboarding guides, or feature documentation.