pr:gen-linear

Generate formatted pull-request descriptions linked to Linear issues from committed changes.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/sorafujitani/claudedot --skill pr-gen-linear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr:gen-linear
Source: https://github.com/sorafujitani/claudedot/tree/main/skills/pr%3Agen-linear
Command: npx skills add https://github.com/sorafujitani/claudedot --skill pr-gen-linear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically generate a Linear-integrated PR by analyzing the current git state and the associated Linear issue, enabling seamless linkage and standard-format PRs.

Core Features & Use Cases

  • Extract Linear issue IDs from branch names and construct a direct Linear URL for the PR
  • Analyze only pushed commits and changes from the branch to produce a deterministic PR
  • Prepare and format PR content to align with toridori standard PR structure for quick review

Quick Start

On a feature branch, run the PR generation flow to create a Linear-integrated PR automatically.

Frequently Asked Questions about pr:gen-linear

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

FAQPage Schema
How do I auto-generate a Linear-integrated pull request from my git branch?

To auto-generate a Linear-integrated pull request, the Skill analyzes your pushed git commits, extracts the Linear issue ID from the branch name, and builds a Linear URL to attach to the PR. It structures changes by category and prepares a gh pr create command.

How does extracting a Linear issue ID from a branch name work for PR generation?

Extracting a Linear issue ID from a branch name works by parsing the branch text to find the identifier, then constructing a direct Linear URL. This URL is inserted into the PR body to link the pull request directly to its corresponding Linear issue.

What's the best way to format pull request content to align with standard PR structure?

The best way to format pull request content is to analyze pushed commits and categorize changes from the branch. This Skill structures changes by category, documents the rationale, and prepares deterministic PR content to align with the standard format for quick review.

Do I need to push my git commits before generating a Linear PR?

Yes, you need to push your git commits before generating a Linear PR. The Skill operates specifically on pushed commits to analyze the current git state and produce a deterministic gh pr create command for submission.

Can I use this PR generation flow with unpushed local git commits?

No, you cannot use this PR generation flow with unpushed local git commits. The Skill explicitly analyzes only pushed commits and changes from the branch to ensure the generated PR reflects the actual remote state.

Why does my generated PR include a direct link to a Linear issue?

Your generated PR includes a direct link to a Linear issue because the Skill extracts the Linear issue ID from your branch name and constructs a Linear URL. This ensures seamless linkage between the pull request and the tracking issue.