Create GitHub pull requests with standardized title format and draft status. Use when the user requests to create a PR. This skill uses gh command to create PRs with specific title format '[base-branch] type: description' and generates concise bullet-point descriptions from git changes.
npx claudepluginhub kkhys/claude-code-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/commit-types.mdCreate GitHub pull requests following a standardized format with proper Conventional Commits types and draft status.
Check the current branch and merge target:
# Get current branch
git branch --show-current
# Check remote tracking and base branch
git status
Collect information about the changes:
# Get commit history from base branch
git log origin/main..HEAD --oneline
# Get detailed diff from base branch
git diff origin/main...HEAD --stat
git diff origin/main...HEAD
Replace origin/main with the actual base branch (e.g., origin/master, origin/develop).
Before generating a description, check if the project has a PR template. If found, always use it as the PR body structure.
# Search for PR template (check all standard locations, case-insensitive)
find . -maxdepth 1 -iname "pull_request_template.md" -o \
-path "./.github" -prune -false | head -1
find ./.github -maxdepth 1 -iname "pull_request_template.md" 2>/dev/null | head -1
find ./docs -maxdepth 1 -iname "pull_request_template.md" 2>/dev/null | head -1
# Also check for multiple templates directory
ls .github/PULL_REQUEST_TEMPLATE/ 2>/dev/null
ls PULL_REQUEST_TEMPLATE/ 2>/dev/null
ls docs/PULL_REQUEST_TEMPLATE/ 2>/dev/null
Template search order (first match wins):
pull_request_template.md (root, case-insensitive).github/pull_request_template.md (case-insensitive)docs/pull_request_template.md (case-insensitive).github/PULL_REQUEST_TEMPLATE/ (multiple templates directory)PULL_REQUEST_TEMPLATE/ (root)docs/PULL_REQUEST_TEMPLATE/If a template is found:
<!-- ... -->)If multiple templates exist in a directory:
If no template is found:
Analyze the changes and determine the appropriate Conventional Commits type:
Format: [base-branch] type: description
Components:
[base-branch]: The target branch name (e.g., main, master, develop)type: Conventional Commits type (feat, fix, chore, docs, refactor, test, perf, style, ci, build)description: Concise summary of changes in lowercaseExamples:
[main] feat: add user authentication system[main] fix: resolve null pointer in login handler[develop] refactor: extract validation logicGenerate a concise bullet-point list of main changes:
Format:
- Main change 1
- Main change 2
- Main change 3
Guidelines:
Example:
- Add JWT authentication middleware
- Implement user login and logout endpoints
- Add password hashing with bcrypt
Before creating the PR, ensure the current branch is pushed to the remote repository:
# Check if branch has remote tracking
git rev-parse --abbrev-ref @{upstream} 2>/dev/null
# If no upstream or unpushed commits, push the branch
git push -u origin $(git branch --show-current)
Important:
-u flag to set up tracking relationshipUse gh command to create the draft PR:
gh pr create \
--title "[main] feat: add user authentication" \
--body "- Add JWT authentication middleware
- Implement user login and logout endpoints
- Add password hashing with bcrypt" \
--draft \
--assignee kkhys
Important:
--draft flag to create draft PR--assignee kkhys flag to assign PR to kkhys (REQUIRED)gh pr create \
--title "[main] feat: add user authentication" \
--body "$(cat <<'EOF'
- Add JWT authentication middleware
- Implement user login and logout endpoints
- Add password hashing with bcrypt
EOF
)" \
--draft \
--assignee kkhys
User Request: "PRを作成して"
Workflow:
feature/user-authmainfeat[main] feat: add user authentication systemUser Request: "create a PR"
Workflow:
bugfix/null-pointermainfix[main] fix: resolve null pointer in login handlerUser Request: "make a pull request"
Workflow:
feature/api-improvementsdevelopfeat (primary purpose is new functionality)[develop] feat: add data export endpointFor detailed guidelines on selecting the appropriate type, see commit-types.md.
Quick Reference:
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.