open-pr

Create GitHub pull requests from conversation context with tagged titles and summaries.

1|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/fengqiyu0317/assassyn --skill open-pr-fengqiyu0317
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: open-pr
Source: https://github.com/fengqiyu0317/assassyn/tree/main/assassyn-master/.claude/skills/open-pr
Command: npx skills add https://github.com/fengqiyu0317/assassyn --skill open-pr-fengqiyu0317

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically transform conversation context into ready-to-submit GitHub pull requests with consistent formatting and tag selection, reducing manual drafting time and human error.

Core Features & Use Cases

  • Structured PR templates to enforce titles and sections
  • Tag-aware formatting to apply proper labels and context
  • Context extraction from discussions to populate PR content

Quick Start

Invoke the open-pr skill in a conversation and confirm the generated PR draft

Frequently Asked Questions about open-pr

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

FAQPage Schema
How do I generate a GitHub pull request from a conversation automatically?

To automate pull request creation, this Skill extracts context from your development conversation and populates a structured GitHub PR template. It automatically formats the title, summary, change log, and testing notes based on the dialogue context.

How does tag-aware formatting work for GitHub pull requests?

Tag-aware formatting relies on a central tag definitions document to select the correct label for your pull request. It enforces a consistent title format combining the tag with an issue reference, ensuring proper categorization and context for code review workflows.

Can I require an issue reference when creating a pull request draft?

Yes, this Skill requires an issue reference in the pull request title whenever possible. It formats titles using the [tag][#issue] structure, linking the generated PR directly to the relevant issue tracked in your GitHub repository.

Does this PR automation tool work without external dependencies?

Yes, this Skill operates without external dependencies to generate well-formed pull requests. It applies to software development dialogues by extracting context directly from the conversation to populate titles, summaries, change logs, and testing notes.

What is the best way to enforce consistent PR templates for code review?

The best way to enforce consistency is using a structured template that automatically applies tag-aware formatting. This Skill standardizes pull request titles and sections like summaries and change logs, reducing human error during code review preparation.

What are the limitations of generating pull requests from conversation context?

A limitation is that the generated pull request requires a central tag definitions document to select the correct label. If the conversation context lacks sufficient development details, the automated draft may have incomplete summaries or missing testing notes.