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.

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: 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: 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: If hooks changed → Update README.md and README.zh CN.md Auto Trigger column. Step 3: Draft Commit Message Use the commit helper format: 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: 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: Documentation Update Guidelines Skills Catalog Update Template When adding or modifying skills, use this format for the Skills Catalog: English (README.md): Chinese (README.zh CN.md): 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): Chinese (README.zh CN.md): Language Switch Link Both README files must have the language switch at the top: README.md: README.zh CN.md: PR Description Template When creating a PR, use this template: Common Scenarios Scenario 1: Adding a New Skill Scenario 2: Modifying an Existing Skill Scenario 3: Bug Fix Only 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 <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 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

create-pr