Menu
Open a GitHub pull request for the current branch using this repo's PR template and the gh CLI. Use when asked to open, create, or raise a PR.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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.
| name | open-pr |
| description | Open a GitHub pull request for the current branch using this repo's PR template and the gh CLI. Use when asked to open, create, or raise a PR. |
Open a PR for the current branch. Assume the working branch is correct, gh is installed and
authenticated, and you are in this repo. This is a simple task — keep it to one or two commands and
use GH_PAGER=cat on gh calls to avoid pager hangs.
Preflight (one command): if a PR already exists for this branch, don't create another — just return its URL.
GH_PAGER=cat gh pr list --head "$(git branch --show-current)" --json number,url,state
Compose the PR locally (no shell commands needed):
`Tag`: short description: a backticked feature tag, then a plain sentence-case
summary suitable for release notes (capitalize only the first word). Use "Fix" for bugfixes,
other action verbs (Add, Allow, Show, Enable…) otherwise; don't repeat the tag in the
description. Tags: Core, Course Phases, Authentication, Module Federation, Interview,
Team Allocation, Matching, Assessment, Certificate, Intro Course,
Self Team Allocation, Templating, New Phase, Database, API, Testing,
Documentation, Infrastructure, Deployment, UI/UX, Performance, General (use
General if none fit)..github/pull_request_template.md from the branch's commits
and diff. Keep all headings, helper text, and checklist items; check the boxes that are true
([x]). Use backticks for literal commands, paths, and branch names. Don't add emojis to the
title or new body text (keep any emojis already in the template). Write the body to a temp file
in the repo (e.g. .pr_body_tmp.md) with your editor — never outside the repo.Create the PR with a single command (pushes the branch if needed):
git push -u origin HEAD 2>/dev/null; GH_PAGER=cat gh pr create --base main --head "$(git branch --show-current)" --title "<title>" --body-file .pr_body_tmp.md
Delete .pr_body_tmp.md and report the PR URL.