playbooks

home / skills / duc01226 / easyplatform / pr

pr skill

/.claude/skills/pr

This skill helps you create a pr with the standard format, including summary, changes, test plan, and reviewers.

npx playbooks add skill duc01226/easyplatform --skill pr

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.5 KB
---
name: pr
description: "[Git & Release] ⚡ Create a pull request with standard format"
argument-hint: [options]
infer: true
---

# Create Pull Request: $ARGUMENTS

Create a pull request with the standard EasyPlatform format.

## Steps

1. **Check current branch status:**
   - Run `git status` to see all changes
   - Run `git diff` to review modifications
   - Ensure all changes are committed

2. **Analyze commits:**
   - Run `git log --oneline -10` to see recent commits
   - Identify all commits to include in the PR

3. **Create PR with standard format:**
   ```
   gh pr create --title "[Type] Brief description" --body "$(cat <<'EOF'
   ## Summary
   - Bullet points describing changes

   ## Changes
   - List of specific changes made

   ## Test Plan
   - [ ] Unit tests added/updated
   - [ ] Manual testing completed
   - [ ] No regressions introduced

   ## Related Issues
   - Closes #issue_number (if applicable)

   Generated with Claude Code
   EOF
   )"
   ```

4. **PR Title Format:**
   - `[Feature]` - New functionality
   - `[Fix]` - Bug fix
   - `[Refactor]` - Code improvement
   - `[Docs]` - Documentation only
   - `[Test]` - Test changes only

## Notes

- Ensure branch is pushed before creating PR
- Target branch is usually `develop` or `master`
- Add reviewers if specified in $ARGUMENTS

## IMPORTANT Task Planning Notes

- Always plan and break many small todo tasks
- Always add a final review todo task to review the works done at the end to find any fix or enhancement needed

Overview

This skill creates a pull request using a standardized EasyPlatform format to ensure consistent titles, bodies, and review checkpoints. It automates the gh CLI command construction and helps enforce branch, commit, and testing conventions before opening a PR. Ideal for teams that require predictable PR content and checklist-driven reviews.

How this skill works

The skill inspects the current git branch, recent commits, and working tree status to ensure changes are committed and pushed. It then assembles a templated PR body (Summary, Changes, Test Plan, Related Issues) and runs the gh pr create command with a formatted title prefix like [Feature], [Fix], or [Refactor]. It can add reviewers and target the appropriate base branch such as develop or master.

When to use it

  • Opening a new feature or bugfix pull request
  • Standardizing PRs across a team or organization
  • Ensuring PRs include test plans and related issues
  • Automating PR creation from CI or local workflows
  • Quickly creating small, checklist-driven PRs

Best practices

  • Run git status and git diff and commit all changes before creating a PR
  • Use git log --oneline -10 to confirm included commits and squash if necessary
  • Choose the correct title prefix: [Feature], [Fix], [Refactor], [Docs], or [Test]
  • Push the branch to the remote and set the correct target branch (develop or master)
  • Populate the Test Plan checklist and reference closing issue numbers when applicable

Example use cases

  • Create a feature PR with a clear summary and list of changes for reviewers
  • Open a hotfix PR using [Fix] to indicate urgency and scope
  • Standardize documentation updates using the [Docs] prefix and a short test plan
  • Run from a local script or CI pipeline to auto-generate PRs after successful builds/tests
  • Create a refactor PR that highlights code improvements without functional changes

FAQ

What title prefixes should I use?

Use [Feature] for new functionality, [Fix] for bug fixes, [Refactor] for code improvements, [Docs] for documentation-only changes, and [Test] for test changes.

What checks should I complete before creating the PR?

Ensure all changes are committed and pushed, review git diff and recent commits, and complete or plan unit and manual tests listed in the Test Plan checklist.