메뉴
Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | blueprint |
| description | Use when the user asks to analyze, document, inspect, or understand the database schema. Connects to the live database (Docker or direct) and reads ORM code to produce comprehensive docs/DB.md with tables, relations, indexes, and query patterns. |
You are PolyForge's database analyst. Produce comprehensive database documentation.
/blueprint Auto-detect and analyze all databases
/blueprint --code-only Code analysis only (no live connection)
/blueprint --table users Focus on a specific table/collection
Use pre-loaded config for database.type, database.connectionMethod, database.containerName.
If not configured: auto-detect from docker-compose.yml, .env.*, ORM config files.
Scan ORM entities/models and migration directories. Build schema evolution timeline. Identify query patterns from repositories/services.
Ask first — show masked connection string, then call AskUserQuestion — "Connect to this database?" with options: "Connect" / "Skip live query" / "Other". See @skills/shared/common-patterns.md § "User Questions — AskUserQuestion ONLY".
Docker: docker compose ps to check container. If stopped, call AskUserQuestion — "Container is stopped." with options: "Start it" / "Skip" / "Other".
Query templates: @skills/blueprint/sql-queries.md
Under 15 tables: Analyze inline — no subagents.
Over 15 tables: Batch tables into groups of 5-8, spawn [model: sonnet] subagent per batch (max 3 concurrent). Each returns:
[{ "table": "", "columns": [], "indexes": [], "relations": [], "queryPatterns": [], "enumValues": {}, "warnings": [] }]
docs/DB.mdMerge results. Structure: overview → per-table details → mermaid relationship map → anti-patterns → large table warnings.
Cross-reference live data with ORM: flag orphaned tables (in DB, missing ORM) and pending migrations (in ORM, missing DB).
Backup existing docs/DB.md to tmp/. Add verification timestamp. Compact after generation.
Use when the user asks to analyze, audit, review, or check code quality across the project. Performs full codebase analysis — detects bad patterns, security flaws, performance issues, misconfigurations — and generates a prioritized report in docs/ANALYSIS-{date}.md.
Use when the user wants to set up, create, inspect, or manage PolyForge nocturnal routines — the banked embers that keep the forge working after hours. Subcommands: "embers light" installs/configures nightly routines, "embers cast" creates a custom routine, "embers watch" inspects logs/telemetry, "embers tend" lists/suspends/resumes/deletes/runs them.
Use when the user asks to generate, update, or refresh project documentation, CLAUDE.md, context files, or scoped rules. Creates Claude-optimized documentation with a short CLAUDE.md (<200 lines), detailed docs/CONTEXT.md, and path-scoped rules.
Use when the user asks to clean up, squash, reorganize, or rewrite commit history on the current branch before a PR. Groups messy commits into logical, reviewable units while preserving meaningful history.
Use when the user asks to review a PR, check a pull request, review a GitHub issue, review a Jira ticket, look at changes before merge, or audit code quality. Auto-detects the item type (PR, GitHub issue, Jira ticket) and adapts the review accordingly.
Use when the user asks to initialize, set up, or configure PolyForge for a project, or when starting work on a project with no .claude/polyforge.json. Scans the project, detects stack and architecture, and generates optimized configuration interactively.