メニュー
Creates pull requests with bilingual documentation checks. Use when user asks to create PR, make a pull request, or submit changes for review. Ensures English and Chinese README files stay in sync when user-facing skill catalog changes require it.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | create-pr |
| description | Creates pull requests with bilingual documentation checks. Use when user asks to create PR, make a pull request, or submit changes for review. Ensures English and Chinese README files stay in sync when user-facing skill catalog changes require it. |
| allowed-tools | Read, Write, Edit, Bash, Grep, AskUserQuestion |
| metadata | {"hooks":{"after_complete":[{"trigger":"session-logger","mode":"auto","reason":"Log PR creation"}]}} |
A skill for creating pull requests with bilingual documentation checks. This skill ensures that English and Chinese documentation stay in sync before code changes are submitted.
This skill activates when you:
Examine all changes in the current branch:
git status
git diff
git log --oneline main..HEAD
Identify:
First, detect if any skills were changed:
# Check if skills/ directory has changes
git diff --name-only main..HEAD | grep "^skills/"
| Change Type | Documentation Action |
|---|---|
| New skill added | Add to skills table in both EN and CN README |
| Skill description changed | Update description in skills table |
| Skill removed | Remove from skills table |
| Skill hooks changed | Update Auto-Trigger column in skills table |
| Internal skill logic only | Skip README update |
| Bug fix with no user impact | Skip README update |
If a skill's metadata.hooks front matter was modified, the Auto-Trigger column in the Skills Catalog must be updated:
# Check if hooks were modified
git diff main..HEAD -- skills/*/SKILL.md | grep -E "^\+.*metadata:|^\+.*hooks:|^\+.*trigger:"
If hooks changed → Update README.md and README.zh-CN.md Auto-Trigger column.
Use the commit-helper format:
<type>(<scope>): <subject>
<body>
<footer>
Types:
feat: New skill or featurefix: Bug fix or correctiondocs: Documentation only changesrefactor: Code refactoringchore: Maintenance tasksRun the following sequence:
# 1. Stage only the intended files
git add <changed-files>
git commit -m "commit message"
# 2. Push to remote
git push -u origin <branch-name>
# 3: Create PR using gh CLI
gh pr create \
--title "PR title" \
--body "PR description"
Before committing or creating the PR, update both README files when the change affects user-facing skill catalog, installation, or workflow behavior:
README.md (English):
README.zh-CN.md (Chinese):
For significant changes, add to CHANGELOG.md:
## [Version] - YYYY-MM-DD
### Added
- New skill: skill-name
### Fixed
- Fixed issue in skill-name
### Changed
- Updated skill-name with new features
When adding or modifying skills, use this format for the Skills Catalog:
English (README.md):
### Category Name
| Skill | Description | Follow-up |
|-------|-------------|--------------|
| **[skill-name](./skills/skill-name/)** | Brief description | Manual / Auto / Background / (keyword: "...") |
Chinese (README.zh-CN.md):
### 类别名称
| 技能 | 描述 | 后续动作 |
|------|------|----------|
| **[skill-name](./skills/skill-name/)** | 简短描述 | 手动 / 自动 / 后台 / (关键词："...") |
| Value | Meaning | Example |
|---|---|---|
Manual | User must invoke | Most development skills |
Auto | Triggers automatically after any skill | session-logger |
Background | Runs non-blocking after related skill | self-improving-agent |
After skill updates | Only triggers when skills are modified | create-pr |
(keyword: "...") | Activates on specific keyword | prd-planner (keyword: "PRD") |
Always update when:
Consider updating when:
Skip updating when:
When adding a new skill to the skills table:
English (README.md):
| **[skill-name](./skills/skill-name/)** | Brief skill description |
Chinese (README.zh-CN.md):
| **[skill-name](./skills/skill-name/)** | 技能简短描述 |
Both README files must have the language switch at the top:
README.md:
English | [简体中文](./README.zh-CN.md)
README.zh-CN.md:
[English](./README.md) | 简体中文
When creating a PR, use this template:
## Summary
<Brief description of what this PR does>
## Changes
- [ ] New skill added
- [ ] Existing skill modified
- [ ] Documentation updated
- [ ] Tests added/updated
## Skills Affected
- `skill-name`: Description of change
## Documentation
- [x] README.md updated
- [x] README.zh-CN.md updated
- [ ] CHANGELOG.md updated (if applicable)
## Test Plan
- [ ] Skill tested in Claude Code
- [ ] Documentation links verified
- [ ] Bilingual translations checked
# 1. Create skill files
mkdir -p skills/new-skill
touch skills/new-skill/SKILL.md
touch skills/new-skill/README.md
# 2. Install or link through the package CLI when possible
apb skills add ./skills/new-skill --scope project --target all --link
# 3. Update README.md (add to skills table)
# 4. Update README.zh-CN.md (add to skills table with translation)
# 5. Commit and push
git add skills/new-skill/ README.md README.zh-CN.md
git commit -m "feat: add new-skill for ..."
git push -u origin feature/add-new-skill
# 6. Create PR
gh pr create --title "feat: add new-skill" --body "..."
# 1. Make changes to skill
vim skills/existing-skill/SKILL.md
# 2. Check if description changed
git diff skills/existing-skill/SKILL.md
# 3. If description changed, update README files
# 4. Commit, push, create PR
# 1. Fix the bug
vim skills/some-skill/SKILL.md
# 2. Commit and push (no README update needed)
git add skills/some-skill/SKILL.md
git commit -m "fix: correct typo in some-skill"
git push
# 3. Create PR
gh pr create --title "fix: correct typo in some-skill"
Before creating the PR, verify:
| Command | Purpose |
|---|---|
git status | Check current state |
git diff | See unstaged changes |
git log main..HEAD | See branch commits |
git add <changed-files> | Stage only intended files |
git commit -m "msg" | Commit with message |
git push -u origin branch | Push to remote |
gh pr create | Create pull request |
API documentation specialist for OpenAPI/Swagger specifications. Use when documenting REST or GraphQL APIs.
Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
Workflow hook metadata for agent-playbook skills. This skill documents trigger intent between skills - DO NOT use directly, and do not assume hooks execute unless the host runtime explicitly supports them.
Reviews pull requests and code changes for quality, security, and best practices. Use when user asks for code review, PR review, or mentions reviewing changes.
Helps write Git commit messages following the Conventional Commits specification. Use this skill when the user asks to commit changes, write commit messages, format commits, or mentions git commits.
Deployment automation specialist for CI/CD pipelines and infrastructure. Use when setting up deployment, configuring CI/CD, or managing releases.