explainx.ainewsletter3.4k
Productivity

create-pr▌

charon-fan/agent-playbook · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/charon-fan/agent-playbook --skill create-pr
0 commentsdiscussion
summary

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.

skill.md

Create PR

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.

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

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

Step 5: Update Documentation (If Required)

After creating the PR, update both README files:

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 | Auto-Trigger |
|-------|-------------|--------------|
| **[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

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

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

---

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

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

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

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
how to use create-pr

How to use create-pr on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add create-pr
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/charon-fan/agent-playbook --skill create-pr

The skills CLI fetches create-pr from GitHub repository charon-fan/agent-playbook and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/create-pr

Reload or restart Cursor to activate create-pr. Access the skill through slash commands (e.g., /create-pr) or your agent's skill management interface.

⚠

Security & Verification Notice

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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

User Story & Requirements Generation

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

Competitive Analysis

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

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

✓

Make data-driven prioritization decisions faster

Stakeholder Communication

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

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client
  • ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • ›Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • ⚠Not validating competitive research—verify facts before sharing
  • ⚠Accepting user stories without involving engineering team
  • ⚠Over-relying on frameworks without qualitative judgment
  • ⚠Not customizing outputs to company culture and communication style
  • ⚠Skipping stakeholder validation of generated requirements

Best Practices▌

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • −Don't publish competitive analysis without fact-checking
  • −Don't finalize user stories without engineering review
  • −Don't make prioritization decisions solely on AI scoring
  • −Don't skip customer validation of generated requirements
  • −Don't ignore company-specific context and culture

💡 Pro Tips

  • ★Provide context: company goals, constraints, customer feedback
  • ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • ★Use skill for 70% generation + 30% customization to company needs

When to Use This▌

✓ 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.

Learning Path▌

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.7★★★★★28 reviews
  • ★★★★★Shikha Mishra· Dec 12, 2024

    Useful defaults in create-pr — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Noah Lopez· Nov 11, 2024

    Solid pick for teams standardizing on skills: create-pr is focused, and the summary matches what you get after install.

  • ★★★★★Rahul Santra· Nov 3, 2024

    create-pr is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Pratham Ware· Oct 22, 2024

    Keeps context tight: create-pr is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • ★★★★★Sofia Haddad· Oct 2, 2024

    create-pr has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • ★★★★★Kaira Verma· Sep 21, 2024

    create-pr fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • ★★★★★Oshnikdeep· Sep 13, 2024

    We added create-pr from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • ★★★★★Ishan White· Sep 9, 2024

    I recommend create-pr for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Charlotte Garcia· Aug 28, 2024

    Useful defaults in create-pr — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Ira Rao· Aug 12, 2024

    We added create-pr from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

showing 1-10 of 28

1 / 3