Agent Skills › evrendom/rudel › pr-creation

pr-creation

GitHub

指导在推送代码前创建 Pull Request 的标准流程，包括运行验证、审查差异、提交代码及使用约定式提交格式生成 PR。

.claude/skills/pr-creation/SKILL.md evrendom/rudel

Trigger Scenarios

用户要求创建 Pull Request 准备将本地更改推送到远程仓库

Install

npx skills add evrendom/rudel --skill pr-creation -g -y

More Options

Non-standard path

npx skills add https://github.com/evrendom/rudel/tree/main/.claude/skills/pr-creation -g -y

Use without installing

npx skills use evrendom/rudel@pr-creation

指定 Agent (Claude Code)

npx skills add evrendom/rudel --skill pr-creation -a claude-code -g -y

安装 repo 全部 skill

npx skills add evrendom/rudel --all -g -y

预览 repo 内 skill

npx skills add evrendom/rudel --list

SKILL.md

Frontmatter

{
    "name": "pr-creation",
    "metadata": {
        "internal": true
    },
    "description": "Use when creating a pull request. Runs verification, reviews changes, and creates the PR with correct metadata. Invoke BEFORE pushing code.",
    "allowed-tools": [
        "Read",
        "Edit",
        "Write",
        "Bash",
        "Glob",
        "Grep",
        "mcp__conductor__GetWorkspaceDiff"
    ]
}

PR Creation Checklist

Follow these steps in order when creating a pull request. Do not skip any step.

1. Run Verification

bun run verify

This runs type checking, linting, and tests across the monorepo.

Do NOT proceed if verification fails. Fix issues first, then re-run.

2. Review the Workspace Diff

Use mcp__conductor__GetWorkspaceDiff with stat: true to see all changed files, then review the full diff to understand the scope of changes.

3. Commit All Changes

Stage and commit all changes. Follow any user instructions about commit message style.

4. Push and Create PR

Push to origin with -u flag if the branch has no upstream
PR title must use conventional commit format (enforced by CI): feat: | fix: | docs: | style: | refactor: | perf: | test: | build: | ci: | chore: | revert:
Use gh pr create --base main with:
- Title under 80 characters
- Description covering ALL changes in the workspace diff (not just the latest commit)
- Keep description concise

gh pr create --base main --title "title here" --body "$(cat <<'EOF'
## Summary
- bullet points describing changes

## Test plan
- [ ] testing steps

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

Common Mistakes to Avoid

Skipping verification: Step 1 is non-negotiable. CI will catch the same failures but slower.
Wrong PR title format: Must be conventional commit format or CI will reject it.
Describing only the latest commit: The PR description should cover the entire branch diff.