wf7-pr_skill

Overview

This skill automates creating or updating a Pull Request after verification passes. It ensures the branch is pushed, generates a concise title and a structured PR body, and records the PR metadata in state.json. It prevents PR creation if verification failed and guides updates for existing PRs.

How this skill works

The skill reads the current work state and ensures the workflow is at or past the verification phase with no failures. It checks for an existing PR for the branch, pushes the branch to origin, builds a title from the kickoff Goal (optionally linking an issue), composes a markdown body from Kickoff/Spec/Plan, and runs gh pr create or gh pr edit as needed. After success it updates state.json with PR number and URL and prints the summary.

When to use it

• You have completed wf6-verify and verification reports show no failures.
• You are ready to publish changes for review and want a structured PR created automatically.
• You need to push a branch and link the PR to the originating issue and docs.
• You want to update an existing PR after making additional commits or changing the description.

Best practices

• Run wf6-verify and confirm no test/build failures before creating a PR.
• Keep PR titles concise (under 72 characters) and include the issue number as (#N).
• Use the Kickoff, Spec, and Plan docs to populate a clear Summary, Changes, and Test Plan.
• If a PR already exists, use the update subcommand to push and optionally edit the description.
• Ensure gh CLI is authenticated (gh auth login) and git remote is configured before running.

Example use cases

• Create a PR automatically after CI verification passes to request code review.
• Push and update an existing PR with new commits and refreshed description after addressing feedback.
• Link the PR to the tracked issue and include Kickoff/Spec/Plan links for reviewers.
• Fail fast when verification has not passed, prompting the user to run the verification step first.