Menu
Create a GitHub pull request from the current branch—commit uncommitted changes, push, and open a PR against main with an auto-generated title and Summary/Testing body sections.
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
Applies project TypeScript conventions and library-grade module boundaries. Use when writing or editing .ts/.tsx files, designing exported APIs or cross-layer contracts, creating reusable modules, or refactoring dependencies between features, packages, services, and adapters.
Analyze project vulnerabilities with pnpm audit and resolve them automatically when a fix version is available; report unfixable deep dependency issues.
Plan and (only after user confirmation) delete remote and matching local git branches whose PR is already merged or closed (not merged) and that have no remaining commits or file changes. Use when the user asks to clean up, prune, or delete merged/closed branches (브랜치 정리, cleanup branches, delete merged branches).
Remove safe git worktrees that have no uncommitted changes and no commits missing from a pull request. Use when the user asks to clean up, prune, or remove worktrees (워크트리 정리, worktree cleanup).
Applies project conventions for Solid.js components, custom hooks, reactivity, and styling. Use when writing or editing Solid.js .tsx/.ts files.
Write and refine Korean text in developer contexts — code comments, AIDEV-NOTE anchors, commit messages, PR descriptions, review replies, design docs, memory notes — so it reads as natural, grammatical Korean a native engineer would write, not as awkward literal translation, broken word order, or forced metaphor. Use whenever producing Korean prose for engineering work, and especially self-review Korean output before finalizing.
| name | new-pr |
| description | Create a GitHub pull request from the current branch—commit uncommitted changes, push, and open a PR against main with an auto-generated title and Summary/Testing body sections. |
| disable-model-invocation | true |
Create a new PR using the steps below.
dev, create a feature/<name> branch.dev as the base branch.If the current branch is not dev, use it as-is and run steps 2-4 above.
Before committing or pushing:
.env, API keys, tokens, passwords), stop and tell the user. Do not commit or push.git push, git merge, etc.). Do not use destructive commands (e.g. git push --force, git reset --hard) unless the user explicitly requests them; ask first if unsure.Include the following sections in the PR body: