Skip to main content
Generalmelodic-software

pull-request

Create a GitHub pull request with full context linking back to the original issue. Use after implementation is complete and ready for review.

Stars
74
Source
melodic-software/claude-code-plugins
Updated
2026-04-07
Slug
melodic-software--claude-code-plugins--pull-request
View on GitHubRaw SKILL.md

// install — copy + paste into any project

mkdir -p .claude/skills && curl -fsSL https://raw.githubusercontent.com/melodic-software/claude-code-plugins/HEAD/plugins/tac/skills/pull-request/SKILL.md -o .claude/skills/pull-request.md

Drops the SKILL.md into .claude/skills/pull-request.md. Works with Claude Code, Cursor, and any agent that loads SKILL.md files from .claude/skills/.

Pull Request Creation

Create a well-formatted pull request that links back to the original issue and includes the implementation context.

PR Format

## Summary

[Brief description of what this PR accomplishes]

## Related Issue

Closes #[issue_number]

## Implementation

[Summary of the approach taken]

## Plan Reference

[Link to or summary of the implementation plan]

## Changes

[High-level list of changes made]

## Testing

[How was this tested / what validation was done]

---

Generated by ADW [adw_id]

Instructions

  1. Parse the provided context to extract:

    • Branch name
    • Issue number
    • Plan file or summary
    • ADW ID if available
  2. Generate a PR title from the issue:

    • Format: [type] Brief description (#issue_number)
    • Example: [feat] Add user authentication (#123)
  3. Generate the PR body following the format above

  4. Create the PR using:

    gh pr create \
      --title "[title]" \
      --body "[body]" \
      --base main \
      --head [branch_name]
    

Input Variables

$ARGUMENTS should contain:

  • Branch name
  • Issue number or URL
  • Plan file path or summary
  • ADW ID (optional)

Example Output

gh pr create \
  --title "[feat] Add OAuth authentication (#123)" \
  --body "## Summary

Implements OAuth authentication with Google provider as specified in issue #123.

## Related Issue

Closes #123

## Implementation

Added OAuth flow using passport.js with Google strategy. Created new auth routes and middleware.

## Plan Reference

Implementation followed specs/feature-oauth-auth.md

## Changes

- Added OAuth configuration
- Created auth routes (/auth/google, /auth/callback)
- Added user session management
- Updated environment variables

## Testing

- Verified OAuth flow works end-to-end
- Tested session persistence
- Ran existing test suite

---

Generated by ADW a1b2c3d4"

Context

$ARGUMENTS