mcpField
U
update-pr

update-pr

github.com/willboosterDevelopment37 installs
Repository

About update-pr

update-pr is an agent skill for revising a pull request’s title and body to match its current scope, motivation, and validation. It uses a command-line invocation and requires a Conventional Commits title prefix.

Key features

  1. 01Draft a replacement PR title
  2. 02Write a complete replacement PR body
  3. 03Use Conventional Commits title prefixes
  4. 04Report the pull request URL

Use cases

  1. 01Refresh a PR description after scope changes
  2. 02Summarize motivation and validation in a PR
  3. 03Standardize a PR title before updating

Install

Copy the command and run it in a terminal.

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

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

Details

From the project README

Update PR workflow

Write the full replacement pull request title and the complete replacement PR body so they reflect the current scope, motivation, and validation. Run update-pr with the title as the first argument and the body on stdin. Finally, report the pull request URL.

bunx @willbooster/agent-skills@latest update-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