A skill for creating pull requests with automatic bilingual documentation updates. This skill ensures that both English and Chinese documentation stay in sync when code changes are submitted.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncreate-prExecute the skills CLI command in your project's root directory to begin installation:
Fetches create-pr from charon-fan/agent-playbook and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate create-pr. Access via /create-pr in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
27
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
27
stars
A skill for creating pull requests with automatic bilingual documentation updates. This skill ensures that both English and Chinese documentation stay in sync when 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 and commit changes
git add .
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"
After creating the PR, update both README files:
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 | Auto-Trigger |
|-------|-------------|--------------|
| **[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
---
🤖 Generated with [Claude Code](https://claude.com/claude-code)
# 1. Create skill files
mkdir -p skills/new-skill
touch skills/new-skill/SKILL.md
touch skills/new-skill/README.md
# 2. Create symlink
ln -s ~/path/to/agent-playbook/skills/new-skill/SKILL.md ~/.claude/skills/new-skill.md
# 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 . |
Stage all changes |
git commit -m "msg" |
Commit with message |
git push -u origin branch |
Push to remote |
gh pr create |
Create pull request |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
ailabs-393/ai-labs-claude-skills
Useful defaults in create-pr — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: create-pr is focused, and the summary matches what you get after install.
create-pr is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: create-pr is the kind of skill you can hand to a new teammate without a long onboarding doc.
create-pr has been reliable in day-to-day use. Documentation quality is above average for community skills.
create-pr fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added create-pr from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend create-pr for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in create-pr — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added create-pr from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 28