AI SummaryDraft PR content with the following additional instructions: $ARGUMENTS Create a PR draft in file based on the current branch changes. 1. Verify branch status:
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "ccexp" skill in my project. Please run this command in my terminal: # Install skill into your project (3 files) mkdir -p .claude/skills/commands && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/SKILL.md "https://raw.githubusercontent.com/nyatinte/ccexp/main/.claude/commands/draft-pr.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/commit.md "https://raw.githubusercontent.com/nyatinte/ccexp/main/.claude/commands/commit.md" && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/commands/create-pr.md "https://raw.githubusercontent.com/nyatinte/ccexp/main/.claude/commands/create-pr.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Draft PR content and write to PR.md file
Context
• Current branch: !git branch --show-current • Remote tracking: !git status -sb • Recent commits on this branch: !git log origin/main..HEAD --oneline • Repository info: !gh repo view --json owner,name
Your task
Create a PR draft in PR.md file based on the current branch changes.
Steps
• Verify branch status: • Ensure current branch is not main/master • Check if there are commits to create PR for • If no commits or on main branch, inform user and exit • Check for existing PR: • Check if PR already exists: gh pr list --head $(git branch --show-current) • If PR exists, get current PR details for comparison • Analyze repository PR style: • Search for past PRs: gh pr list --state merged --limit 10 • Analyze recent PRs for: • Title format and language • Description structure • Common patterns • Load PR template: • Read .github/PULL_REQUEST_TEMPLATE.md if it exists • Use template structure as base • Analyze changes: • Get all commit messages: git log origin/main..HEAD --pretty=format:"%s" • Get detailed diff if needed: git diff origin/main..HEAD --stat • Understand the overall purpose of changes • Create PR.md file: • Follow the template structure (Summary, Why, Changes with AS-IS/TO-BE) • Write clear title (first line) • Write comprehensive description (rest of file) • Match the repository's PR language and style • Include all relevant context • Show draft to user: • Display the created PR.md content • Inform user they can edit PR.md before creating the PR • Suggest using /create-pr command next
Important Notes
• DO NOT create the actual PR - only draft the content in PR.md • Follow the repository's existing PR style and language • Ensure PR.md follows the template format (Summary/Why/Changes) • Make the description comprehensive but concise
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster