メニュー
Add or change a database schema in a PROMPT 2.0 Go service using golang-migrate + sqlc — write the migration and queries, regenerate type-safe Go, and stay green on the migration CI check. Use when adding a table/column, writing SQL queries, or running sqlc.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Scaffold a new PROMPT 2.0 course phase end-to-end — a micro-frontend (clients/) plus a Go microservice (servers/) wired into Module Federation, the workspaces, and docker-compose. Use when asked to add a new course phase, component, or phase module/service.
Add or reuse a shared UI component in PROMPT 2.0 — install shadcn/ui primitives into the shared_library and surface them via @tumaet/prompt-ui-components instead of writing custom UI. Use when adding a button/dialog/table/form or any reusable UI element.
Address unresolved review comments on the current branch's GitHub PR — fetch the open threads, fix the code, and push. Use when asked to handle, resolve, or respond to PR review comments/feedback.
Docker Compose patterns for PROMPT's local multi-service stack — networking, volumes, container security, and debugging. Use when editing docker-compose*.yml, adding a service, or troubleshooting containers.
Create a GitHub release for the PROMPT 2.0 repository. Use this when asked to create, draft, or publish a GitHub release.
Deeper idiomatic Go patterns for PROMPT's services — concurrency (errgroup, context, goroutine leaks), error wrapping, and performance idioms. The go/ rules point here for these; they own the Gin/pgx/sqlc conventions.
SOC 職業分類に基づく
| name | sqlc-migration |
| description | Add or change a database schema in a PROMPT 2.0 Go service using golang-migrate + sqlc — write the migration and queries, regenerate type-safe Go, and stay green on the migration CI check. Use when adding a table/column, writing SQL queries, or running sqlc. |
| argument-hint | <server name, e.g. core | assessment | interview> |
Schema and queries for a Go microservice live under servers/<service>/db/. Migrations run via
golang-migrate (auto-applied on startup), and sqlc generates type-safe Go from the schema +
queries. Work in the target service directory.
servers/<service>/db/migration/, numbered sequentially:
NNNN_short_description.up.sql (zero-padded 4 digits, next number after the highest existing one).NNNN_short_description.down.sql if that service already ships .down.sql files
(ls servers/<service>/db/migration/*.down.sql). If it doesn't, stay up-only to match convention.servers/<service>/db/query/*.sql with sqlc annotations, e.g.:
-- name: GetTutors :many
SELECT * FROM tutors WHERE course_phase_id = $1;
:one, :many, :exec, :execrows as appropriate.servers/<service>/: sqlc generate (config in sqlc.yaml; output lands in db/sqlc/,
package db, pgx/v5). Or make sqlc-<service> from the repo root.import db "github.com/prompt-edu/prompt/servers/<service>/db/sqlc"
tutors, err := queries.GetTutors(ctx, coursePhaseID)
cd servers/<service> && go build ./... && go test ./... (tests use testcontainers-go).detect-migrations.yml workflow flags migration changes — ensure new files follow the
NNNN_*.up.sql naming and that db/sqlc/ was regenerated and committed alongside the migration.db/sqlc/ changes.