dev-workflow-write-pr

Automates GitHub pull-request creation by analyzing diffs and generating descriptions from templates.

Updated Feb 23, 2019
One-click install
npx skills add https://github.com/JohnWebb4/dotfiles --skill dev-workflow-write-pr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-workflow-write-pr
Source: https://github.com/JohnWebb4/dotfiles/tree/main/.cursor/skills/dev-workflow-write-pr
Command: npx skills add https://github.com/JohnWebb4/dotfiles --skill dev-workflow-write-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of creating GitHub pull requests by analyzing changes from the base branch and generating a clear, templated description.

Core Features & Use Cases

  • Analyze diffs to determine base branch and scope.
  • Generate a PR description following Jira or GitHub issue templates.
  • Create the PR if one doesn't exist, or update an existing PR.

Quick Start

Run the workflow from the repo root to generate or push a PR from the current branch.

Frequently Asked Questions about dev-workflow-write-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request creation from local git changes?

You can automate GitHub pull request creation by analyzing local git diffs against the base branch to automatically generate a clear, templated PR description and create the PR if it does not exist.

Does generating a PR description from a diff require GitHub CLI authentication?

Yes, generating a PR description and creating the pull request requires gh CLI authentication, repository access, and a local git environment to compute diffs and push changes.

Can I automatically determine the base branch for a pull request from commit history?

Yes, you can automatically determine the correct base branch for a pull request by analyzing your commit history and deriving the appropriate PR target from the diff.

How do I generate a Jira or GitHub issue style summary for a pull request?

To generate a Jira or GitHub issue style summary for a pull request, the workflow analyzes your code changes against the base branch and composes a templated description based on the diff.

What is the best way to update an existing pull request with new code changes?

The best way to update an existing pull request is to push your local code changes to the branch, allowing the automation to detect the current PR and update its description with the new diff analysis.

Why does automated PR creation fail to compute diffs in my local environment?

Automated PR creation fails to compute diffs if the local git environment is not properly configured, or if the repository lacks the necessary access permissions to compare against the base branch.