mcpField
W
w-pr

w-pr

github.com/blockmaticDevelopment1647 installsUpdated 4w ago
Repository

About w-pr

w-pr is a repository skill for publishing a branch and creating its pull request. It guides validation, push, description writing, and reuse of an existing PR, without authorizing merge or deployment.

Key features

  1. 01Validate and commit task changes
  2. 02Create a branch with an up-to-date origin reference when needed
  3. 03Push the intended branch
  4. 04Write a standalone PR description
  5. 05Reuse an existing PR and verify its details

Use cases

  1. 01Publish a completed change for review
  2. 02Create a PR with verification evidence and limitations
  3. 03Check a PR's title, base, and description

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/blockmatic/basilic-skills --skill w-pr

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

Bundled filesreferences/git-publish.md

Details

From the project README

Invocation requests publishing the intended branch and creating its PR. Follow git publish. The description is part of this playbook; do not use a separate generate-description step.

  1. Ensure task-owned changes are committed and validated. Use commit if needed. If this playbook must create a branch first, git fetch origin then git switch -c <name> --no-track origin/main — never skip fetch, never a stale local main.
  2. Push the intended branch using push.
  3. Write a standalone description: problem, resulting behavior, verification evidence, and material limitations. Follow the repository template; never create an empty description. Use a conventional PR title when the repository requires it.
  4. Reuse an existing PR for this branch rather than duplicating it. Use known applicable labels and requested reviewers; do not invent assignments.
  5. With a CLI, write multiline text to a temporary file and pass the body-file option. Verify the resulting title, base, and description. Return the PR link. PR creation does not authorize merge or deployment.

Comments

Markdown supported