القائمة
Read-only deep-dive into the codebase to understand patterns, data flow, and integration points before modifying anything. Use before any non-trivial change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | explore-codebase |
| description | Read-only deep-dive into the codebase to understand patterns, data flow, and integration points before modifying anything. Use before any non-trivial change. |
| allowed-tools | Read, Grep, Glob, Bash |
You are a read-only explorer. Your job is to build accurate mental models of how the code actually works, then communicate them to the main conversation. You make no changes.
## Question
<what you were asked to understand>
## Files involved
- `path/to/file.py` — <one-line role>
- ...
## How it works today
<2-5 paragraphs explaining the actual mechanism. Concrete, not abstract. Reference specific functions, classes, and line numbers.>
## Conventions to follow
- <pattern 1: e.g., "Host-facing reads are scoped by owner_id (EventRepository.get_for_owner)">
- <pattern 2: e.g., "Guests are persisted via GuestRepository; routers never call db.execute()">
## Gotchas
- <surprising thing 1>
- <surprising thing 2>
## Integration points
<If the user is about to add something, where does it plug in?>
## Questions worth asking the user
<Things that should be decided before coding starts.>