devenv-open-pr

Generate GitHub pull request titles and bodies from implementation plans, git logs, and issues.

Updated Jul 4, 2024

Search Tags:#automation #git #workflow #documentation #pull request #github

Ready to run

npx skills add https://github.com/workinprogress-ai/devenv --skill devenv-open-pr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: devenv-open-pr
Source: https://github.com/workinprogress-ai/devenv/tree/main/copilot/skills/devenv-open-pr
Command: npx skills add https://github.com/workinprogress-ai/devenv --skill devenv-open-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of manually drafting pull requests by automatically synthesizing implementation plans, git history, and issue context into a professional, standardized PR format.

Core Features & Use Cases

Context-Aware Drafting: Automatically pulls data from implementation plans, git diffs, and linked GitHub issues to build a comprehensive PR body.
Standardized Workflow: Enforces conventional commit titles and structured sections like Summary, Key Decisions, and Testing notes.
Use Case: When you finish a phase of work defined in an implementation plan, use this skill to generate a ready-to-review PR that includes all necessary rationale and testing evidence without manual copy-pasting.

Quick Start

Use the devenv-open-pr skill to create a pull request for the current branch based on the active implementation plan.

Frequently Asked Questions about devenv-open-pr

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

FAQPage Schema

How do I automate pull request creation from git logs and an implementation plan?▼

To automate pull request creation, this Skill synthesizes your local implementation plan files, git history, and linked GitHub issues into a structured PR body. It aggregates context-aware data to build comprehensive titles and standardized summaries without manual copy-pasting.

Do I need the GitHub CLI installed to generate structured pull request bodies?▼

Yes, you need the GitHub CLI installed and local access to repository implementation plan files. This Skill requires integration with the GitHub CLI to function correctly and automatically pull linked issue context to build the comprehensive PR body.

What is the best way to ensure my GitHub PRs include decision logs and testing documentation?▼

The best way to ensure PRs include decision logs and testing documentation is using this Skill to enforce standardized code review workflows. It automatically synthesizes your implementation plan rationale and testing evidence into structured sections for every generated pull request.

Can I use this to create a pull request for the current branch based on a specific implementation plan?▼

Yes, you can generate a ready-to-review pull request for the current branch based on your active implementation plan. The Skill pulls data from the plan, git diffs, and linked GitHub issues to build a comprehensive PR body with all necessary context.

Why does automated PR generation require local access to implementation plan files?▼

Automated PR generation requires local implementation plan files because this Skill aggregates data from those plans to build context-aware PR bodies. It synthesizes the plan rationale, git history, and issue context to ensure the pull request contains all necessary decision logs.