mcpField
O
open-pr

open-pr

github.com/willboosterDevelopment50 installs
Repository

About open-pr

open-pr is a workflow skill for developers that commits and pushes local changes before opening a pull request. It structures reviewer-focused PR details, requires a Conventional Commits title prefix, and reports the resulting URL.

Key features

  1. 01Commit and push current branch changes
  2. 02Write reviewer-focused PR descriptions
  3. 03Use Conventional Commits title prefixes
  4. 04Open a PR and report its URL

Use cases

  1. 01Open a PR for completed code changes
  2. 02Summarize scope, motivation, and validation
  3. 03Link a related issue in a PR

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/willbooster/agent-skills --skill open-pr

After installing, type/open-prin Claude Code to confirm it loaded.

Details

From the project README

Open PR workflow

Commit and push any local changes to the current branch. Write a PR body that helps reviewers quickly understand the scope, motivation, and validation. Include the linked issue when applicable, a concise summary of the changes, the reasoning behind them, and how they were tested. Run the following command to open a pull request. Finally, report the PR URL.

bunx @willbooster/agent-skills@latest open-pr "feat: concise PR title" <<'EOF'
Close #<issue>

## Summary

- What changed
- Key scope or affected area
- Any notable tradeoff or limitation

## Why

- Problem being solved
- Reason this approach was chosen

## Testing

- Exact commands run
- Manual verification steps if relevant

## Notes (if needed)

- Breaking changes, rollout concerns, screenshots, or follow-up work
EOF

Note that the prefix of the PR title must follow the Conventional Commits specification:

  • feat: A new feature for the user or API.
  • fix: A bug fix for the user or API.
  • build: Changes that affect the build system or external dependencies (e.g., npm, webpack, typescript).
  • chore: Routine tasks, maintenance, or tooling changes that don't modify source or test files.
  • ci: Changes to CI/CD configuration files and scripts.
  • docs: Documentation-only changes.
  • perf: A code change that improves performance.
  • refactor: A code change that neither fixes a bug nor adds a feature, but improves code structure or readability.
  • style: Changes that do not affect the meaning of the code (e.g., formatting).
  • test: Adding missing tests or correcting existing tests.

Comments

Markdown supported