Automated summary
Creates a GitHub pull request with a Japanese description by analyzing commit history.
Strengths
- Automatically generates title and description from commits
- Uses Japanese for Japanese-speaking teams or projects
- Verifies and pushes the branch if not already remote
- Defaults to main branch but allows custom base
Limitations
- Requires GitHub CLI installed and authenticated
- Quality of generated text depends on commit messages
- Only supports single base branch at a time
When you need to quickly create a well-structured PR with a Japanese description based on recent commits.
If you prefer to manually write the PR description or if using a different Git hosting service.
Security analysis
SafeThe skill only uses standard GitHub CLI commands ('gh pr create', 'gh pr view') for creating pull requests. It does not involve any destructive operations, code execution from external sources, or exfiltration of secrets. The instructions are transparent and align with typical development workflows, posing no security risk.
No concerns found
How this analysis is madeExamples
/pr/pr developname: pr description: Create a pull request with Japanese description arguments:
- name: base description: Base branch (defaults to main) required: false
Pull Request作成スキル
現在のブランチからPull Requestを作成します。Descriptionは日本語で書かれます。
実行手順
- 現在のブランチ名を取得
- ブランチがリモートにpushされているか確認
- されていなければpush
- コミット履歴を確認してPRのタイトルと本文を作成
gh pr createでPRを作成
PRタイトルの決め方
- ブランチの主要な変更内容を簡潔に（50文字以内）
- 日本語で書く
- 動詞で始める（例：「〜を追加」「〜を修正」「〜を改善」）
PR本文の構成
## 概要
[変更の概要を2-3文で]
## 主な変更点
- [変更点1]
- [変更点2]
- [変更点3]
## テスト方法
[動作確認の手順]
## 注意事項
[レビュアーが知っておくべきこと（あれば）]
使用例
# 基本的な使い方
/pr
# ベースブランチを指定
/pr main
# developブランチに対してPRを作成
/pr develop
GitHub CLI コマンド
# PRを作成
gh pr create --base main --title "タイトル" --body "本文"
# PRの状態を確認
gh pr view
# PRのURLを取得
gh pr view --json url -q .url
実装のポイント
- コミットメッセージを解析してPR本文を自動生成
- 複数のコミットがある場合は、それぞれの変更をリストアップ
- Conventional Commitsの絵文字は除去して見やすく
- 日本語で統一された説明
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/create-pr-in-japanese-mrwak91f' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/create-pr-in-japanese-mrwak91f/download' --output '.skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md.part' && mv '.skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md.part' '.skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md' && test -s '.skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/create-pr-in-japanese-mrwak91f' '.claude/skills/pr'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/create-pr-in-japanese-mrwak91f'openskills read 'create-pr-in-japanese-mrwak91f'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/create-pr-in-japanese-mrwak91f/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.