메뉴
Create and manage pull requests with submodule-aware branch handling, auto-generated titles and descriptions from commit history, and safety-first push behavior. Use when asked to open a PR, check PR status, push a branch, or prepare changes for review.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Prepare and execute high-quality Conventional Commits from working tree changes with repository-aware commit scoping (root repo and submodules) and atomic commit planning. Use when asked to commit, split commits, draft commit messages, or organize staged/unstaged changes into safe commit units.
Design and implement code changes end-to-end, from requirements clarification through implementation, validation, and documentation updates. Use when writing new code, extending features, fixing bugs, or making structured code changes where correctness, maintainability, and clear tradeoffs matter.
Add or improve code and repository documentation so behavior, constraints, and usage are clear and current. Use when asked to write/update docs, docstrings, inline rationale comments, architecture notes, or change-related documentation for code updates.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Install skills from skills.sh, rename to short names, and track originals for updates.
Run repository linting and formatting checks, fix lint failures, and verify a clean result. Use when asked to lint code, resolve style/tooling violations, or make CI lint checks pass across changed files or whole repositories.
| name | pull-request |
| description | Create and manage pull requests with submodule-aware branch handling, auto-generated titles and descriptions from commit history, and safety-first push behavior. Use when asked to open a PR, check PR status, push a branch, or prepare changes for review. |
repo (optional): constrain scope to one repo path (for example backend, frontend, core, or . for the root repo).mode (optional): create (default), status, or update.branch (optional): branch name to use. Auto-generated from commits if omitted.base (optional): target branch. Defaults to main.draft (optional): open as draft PR when true.repo is given, operate in that submodule directory.gh repo view).git status — confirm working tree state (warn if uncommitted changes exist).git branch --show-current — identify current branch.git log --oneline main..HEAD — collect commits that will be in the PR.git diff main...HEAD --stat — summarize file changes.main, create and checkout a new branch.<prefix>/<short-description> using kebab-case.feat commits -> feat/, fix commits -> fix/).-u to set upstream tracking: git push -u origin <branch>.type(scope): summary. Single commit -> use its subject line directly. Multiple commits -> determine the dominant type (feat if any feats, fix if all fixes, chore/refactor/etc. as appropriate) and summarize the theme. Use the same types as commits: feat, fix, refactor, test, docs, chore, perf, ci, build, style. Scope is optional but encouraged when changes target a specific area. Keep under 72 characters.## Summary
<bulleted list derived from commit messages>
gh pr create --title "<title>" --base <base> --body "<body>".--draft flag when requested.status: run gh pr status in the target repo, or gh pr view <number> for a specific PR.update: push latest commits and run gh pr view to confirm CI status after push.--force, --force-with-lease).main, production, uat, release/*).<prefix>/<short-description> using kebab-case.feat, fix, refactor, test, docs, chore, perf, ci, build, or a person's name.