
Create Pr
Contributors shipping changes to repos that keep English and Chinese READMEs in sync who want PR creation with doc updates and a verification checklist.
Overview
Create PR is an agent skill for the Ship phase that creates pull requests with automatic bilingual README updates and a verification checklist.
Install
npx skills add https://github.com/charon-fan/agent-playbook --skill create-prWhat is this skill?
- Six-step workflow: analyze git diff → determine doc updates → update EN/CN READMEs → verify checklist → commit and push
- Automatic change analysis from git diff before deciding documentation impact
- Keeps README.md and README.zh-CN.md synchronized for bilingual agent-playbook-style repos
- Ships a consistent PR description template and pre-submission verification checklist
- Documents symlink install under ~/.claude/skills for Claude Code
- Documented 6-stage PR workflow from analyze changes through create PR
- Updates 2 readme files: README.md and README.zh-CN.md
Adoption & trust: 539 installs on skills.sh; 58 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You finished a code change but bilingual READMEs and PR description format are easy to forget, leaving reviewers without context.
Who is it for?
Solo contributors on agent-playbook or similar repos who routinely ship via PR and maintain README.md plus README.zh-CN.md together.
Skip if: Repos without bilingual readme requirements, changes that skip git entirely, or teams that use alternate PR tooling without local diff-and-doc workflow.
When should I use this skill?
You are ready to commit and open a pull request and need bilingual README updates driven from the git diff.
What do I get? / Deliverables
You push a branch with synchronized EN/CN docs, a completed checklist, and a templated PR ready for review.
- Updated README.md and README.zh-CN.md reflecting the change
- Commit and push on a feature branch
- Pull request with template-based description and verified checklist
Recommended Skills
Journey fit
Ship is where code leaves your machine via reviewable pull requests with consistent descriptions and doc parity. Review is the canonical shelf because the skill orchestrates diff analysis, doc sync, checklist verification, and PR submission—not production deploy or security audit.
How it compares
Use as a repo-specific PR-and-docs ritual in Claude Code, not as a generic GitHub App or standalone code-review skill.
Common Questions / FAQ
Who is create-pr for?
Maintainers and contributors using Claude Code on projects that require paired English and Chinese README updates when opening pull requests.
When should I use create-pr?
Use it in Ship review when your branch is ready: after implementing a change and before asking for merge, to sync docs and open the PR.
Is create-pr safe to install?
Review the Security Audits panel on this Prism page; the skill uses git and filesystem access—only symlink trusted paths and inspect diffs before push.
SKILL.md
READMESKILL.md - Create Pr
# Create PR A Claude Code skill for creating pull requests with automatic bilingual documentation updates. ## Overview This skill streamlines the PR creation process for the agent-playbook repository. It ensures that both English and Chinese documentation remain synchronized whenever code changes are submitted. ## Features - **Automatic Change Analysis**: Examines git diff to understand what changed - **Documentation Sync**: Updates both README.md and README.zh-CN.md - **Bilingual Support**: Maintains parity between English and Chinese docs - **PR Template**: Provides consistent PR description format - **Verification Checklist**: Ensures nothing is missed before submission ## Installation ```bash mkdir -p ~/.claude/skills ln -s ~/Documents/code/GitHub/agent-playbook/skills/create-pr ~/.claude/skills/create-pr ``` ## Workflow ``` ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ Analyze │ -> │ Determine │ -> │ Update Docs │ │ Changes │ │ Updates │ │ (Both EN/CN) │ └─────────────────┘ └─────────────────┘ └─────────────────┘ │ v ┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐ │ Create PR │ <- │ Commit & │ <- │ Verify │ │ │ │ Push │ │ Checklist │ └─────────────────┘ └─────────────────┘ └─────────────────┘ ``` ## Usage ### Basic Usage ```bash # Simply ask Claude to create a PR "Please create a PR for my changes" ``` The skill will: 1. Analyze all changes 2. Determine if documentation updates are needed 3. Update both README files 4. Commit and push 5. Create the PR ### With Specific Focus ```bash "Create a PR for the new skill router" ``` The skill will focus on the skill-router changes and update documentation accordingly. ## Documentation Update Rules | Change Type | Update Required | |-------------|-----------------| | New skill added | ✅ Yes - Add to both READMEs | | Skill removed | ✅ Yes - Remove from both READMEs | | Skill description changed | ✅ Yes - Update both READMEs | | Bug fix | ❌ No - Unless user-facing | | Internal refactor | ❌ No - Documentation unchanged | ## PR Description Template ```markdown ## Summary <Brief description of the changes> ## Changes - [ ] New skill added - [ ] Existing skill modified - [ ] Documentation updated ## Documentation - [x] README.md updated - [x] README.zh-CN.md updated 🤖 Generated with [Claude Code](https://claude.com/claude-code) ``` ## Bilingual Documentation ### Adding a New Skill **README.md (English):** ```markdown | **[skill-name](./skills/skill-name/)** | Skill description | ``` **README.zh-CN.md (Chinese):** ```markdown | **[skill-name](./skills/skill-name/)** | 技能描述 | ``` ### Language Switch Links Both files must have the switch link at the top: **README.md:** ```markdown English | [简体中文](./README.zh-CN.md) ``` **README.zh-CN.md:** ```markdown [English](./README.md) | 简体中文 ``` ## Examples ### Example 1: Adding a New Skill **Input:** ``` "I've created a new skill called skill-router. Please create a PR." ``` **Skill Actions:** 1. Analyzes the skill-router directory 2. Adds skill-router to Meta Skills table in README.md 3. Adds skill-router to 元技能 table in README.zh-CN.md 4. Commits all changes 5. Pushes to remote branch 6. Creates PR with description ### Example 2: Bug Fix **Input:** ``` "I fixed a typo in debugger skill. Create a PR." ``` **Skill Actions:** 1. Analyzes the change (typo fix only) 2. Determines no documentation update needed 3. Commits and pushes 4. Creates PR with simple description ## Verification Checklist Before creating PR, the skill verifies: - [ ] All changes are committed - [ ] Branch is pushed to remote - [ ] Commit messages follow Conventional Commits - [ ] README.md updated (if needed) - [ ] README.zh-CN.md updated (if needed) - [ ] Languag