Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
charon-fan avatar

Create Pr

charon-fan/agent-playbook

  • 625 installs
  • 65 repo stars
  • Updated June 21, 2026
  • charon-fan/agent-playbook

create-pr is a Claude Code skill that automatically generates bilingual documentation updates and creates consistent pull requests with verified change analysis for the agent-playbook repository.

About

create-pr streamlines pull request creation for the charon-fan/agent-playbook repository with automatic change analysis and bilingual documentation sync. The skill examines git diff to understand code changes, updates both README.md and README.zh-CN.md to maintain English–Chinese parity, fills a consistent PR description template, and runs a verification checklist before submission. Developers reach for create-pr when submitting agent-playbook changes and need EN/ZH docs kept synchronized without manual diff review and README editing on every PR.

  • Automatic git diff analysis to detect code and documentation changes
  • Synchronizes both README.md and README.zh-CN.md to maintain bilingual parity
  • Applies a standardized PR template with verification checklist
  • 6-step workflow: analyze → determine updates → sync docs → verify → commit/push → create PR
  • Ensures nothing is missed before PR submission

Create Pr by the numbers

  • 625 all-time installs (skills.sh)
  • Ranked #96 of 739 Git & Pull Requests skills by installs in the Skillselion catalog
  • Security screen: LOW risk (skills.sh audit)
  • Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/charon-fan/agent-playbook --skill create-pr

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs625
repo stars★ 65
Security audit3 / 3 scanners passed
Last updatedJune 21, 2026
Repositorycharon-fan/agent-playbook ↗

How do you create PRs with bilingual docs?

Automatically generate bilingual documentation updates and create consistent pull requests with verified change analysis.

Who is it for?

Contributors to charon-fan/agent-playbook who must keep English and Chinese README files synchronized on every code change PR.

Skip if: Repositories without bilingual README.zh-CN.md requirements or teams using fully automated release bots without doc sync needs.

When should I use this skill?

User wants to create a pull request in agent-playbook with automatic bilingual README updates from git diff.

What you get

Pull request with synced README.md and README.zh-CN.md, templated description, and completed verification checklist.

  • Pull request with templated description
  • Updated bilingual README files

By the numbers

  • Syncs 2 README files: README.md and README.zh-CN.md

Files

SKILL.mdMarkdownGitHub ↗

Create PR

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.

When This Skill Activates

This skill activates when you:

  • Ask to create a pull request or PR
  • Say "submit my changes" or "push and create PR"
  • Mention "make a PR" or "open a pull request"
  • Want to submit code for review

PR Creation Workflow

Step 1: Analyze Changes

Examine all changes in the current branch:

git status
git diff
git log --oneline main..HEAD

Identify:

  • Modified files: What was changed?
  • New files: What was added?
  • Deleted files: What was removed?
  • Impact area: Which skills or features are affected?

Step 2: Determine Documentation Updates

Check for Skill Changes

First, detect if any skills were changed:

# Check if skills/ directory has changes
git diff --name-only main..HEAD | grep "^skills/"

Decision Matrix

Change TypeDocumentation Action
New skill addedAdd to skills table in both EN and CN README
Skill description changedUpdate description in skills table
Skill removedRemove from skills table
Skill hooks changedUpdate Auto-Trigger column in skills table
Internal skill logic onlySkip README update
Bug fix with no user impactSkip README update

Auto-Trigger Changes Require 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.

Step 3: Draft Commit Message

Use the commit-helper format:

<type>(<scope>): <subject>

<body>

<footer>

Types:

  • feat: New skill or feature
  • fix: Bug fix or correction
  • docs: Documentation only changes
  • refactor: Code refactoring
  • chore: Maintenance tasks

Step 4: Create the Pull Request

Run 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"

Step 5: Update Documentation (If Required)

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):

  • Add new skills to appropriate category table
  • Update project structure if needed
  • Keep language switch link at top

README.zh-CN.md (Chinese):

  • Mirror all English changes
  • Translate skill descriptions
  • Maintain same structure and formatting

Step 6: Update Changelog (Optional)

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

Documentation Update Guidelines

Skills Catalog Update Template

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/)** | 简短描述 | 手动 / 自动 / 后台 / (关键词："...") |

Auto-Trigger Column Values

ValueMeaningExample
ManualUser must invokeMost development skills
AutoTriggers automatically after any skillsession-logger
BackgroundRuns non-blocking after related skillself-improving-agent
After skill updatesOnly triggers when skills are modifiedcreate-pr
(keyword: "...")Activates on specific keywordprd-planner (keyword: "PRD")

When to Update README

Always update when:

  • Adding a new skill
  • Removing a skill
  • Changing skill names or descriptions
  • Restructuring the skills directory

Consider updating when:

  • Adding significant features to existing skills
  • Changing installation instructions
  • Modifying project structure

Skip updating when:

  • Internal code refactoring with no user impact
  • Minor typo fixes
  • Test file changes

Bilingual Update Format

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/)** | 技能简短描述 |

Language Switch Link

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) | 简体中文

PR Description Template

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

Common Scenarios

Scenario 1: Adding a New Skill

# 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 "..."

Scenario 2: Modifying an Existing Skill

# 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

Scenario 3: Bug Fix Only

# 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"

Verification Checklist

Before creating the PR, verify:

  • [ ] All changes are committed
  • [ ] Branch is pushed to remote
  • [ ] Commit messages follow Conventional Commits
  • [ ] README.md is updated if needed
  • [ ] README.zh-CN.md is updated if needed
  • [ ] Language switch links are present in both READMEs
  • [ ] New skills have symlinks created
  • [ ] PR title is clear and descriptive
  • [ ] PR description includes summary and changes

Quick Reference

CommandPurpose
git statusCheck current state
git diffSee unstaged changes
git log main..HEADSee branch commits
git add <changed-files>Stage only intended files
git commit -m "msg"Commit with message
git push -u origin branchPush to remote
gh pr createCreate pull request

Tips

1. Commit first, PR later: Always commit changes before creating PR 2. Small PRs: Keep PRs focused on a single change 3. Clear titles: Use Conventional Commits in PR titles 4. Bilingual sync: Always update both README files together 5. Test skills: Verify skills work before submitting PR

Related skills

juliusbrusseeCaveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.264k92.8kmattpocockGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.164k187kmattpocockResolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.160k187kobraUsing Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.145k261kgithubGit CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.2k37kwarpdotdevResolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.15.6k147

FAQ

Which files does create-pr keep synchronized?

create-pr updates both README.md and README.zh-CN.md to maintain English and Chinese documentation parity whenever code changes are submitted via pull request.

How does create-pr analyze changes?

create-pr examines the git diff to understand what changed in the codebase, then determines which documentation sections in both README files need corresponding updates.

What repository is create-pr designed for?

create-pr targets the charon-fan/agent-playbook repository, streamlining PR creation with bilingual doc sync, a PR template, and a pre-submission verification checklist.

Is Create Pr safe to install?

skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Git & Pull Requestsgitintegrations
Browse by category
AI & AgentsFrontend & DesignBackend & DataDev ToolsAutomationTesting & ReviewSecurityMonitoring & CloudDocs & Planning
Design & frontend
Design systemsAnimation & motionAccessibility (a11y)CSS & TailwindUI designUXDesign to codeshadcn/uiLanding pagesBest design skills
Most searched skills
find-skillscavemanfrontend-designbrainstormingsystematic-debuggingstop-slopemil-design-engui-ux-pro-maxkarpathy-guidelinesweb-design-guidelinesreact-best-practicesgrill-meimprovemicrosoft-foundryagent-browser
Browse all listings
All agent skillsAll MCP serversAll marketplacesAll plugins

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.