submitting-pull-requests

Create and submit GitHub pull requests with context from Linear issues and commits.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/blaknite/agent-skills --skill submitting-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: submitting-pull-requests
Source: https://github.com/blaknite/agent-skills/tree/main/submitting-pull-requests
Command: npx skills add https://github.com/blaknite/agent-skills --skill submitting-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of creating and submitting GitHub pull requests, ensuring they are well-structured, context-rich, and adhere to project guidelines, saving developers time and improving review quality.

Core Features & Use Cases

  • Automated PR Creation: Generates PRs using the GitHub CLI with context from commits, issues, and templates.
  • Contextual Descriptions: Drafts PR bodies incorporating Linear issue details, commit messages, and code changes.
  • Reviewer Assignment: Prompts for and adds specified reviewers.
  • Use Case: After committing changes for a new feature linked to a Linear issue, use this skill to automatically create a PR with a detailed description and assign it to your team lead for review.

Quick Start

Use the submitting-pull-requests skill to create a pull request for the current branch.

Frequently Asked Questions about submitting-pull-requests

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

FAQPage Schema
How do I automate GitHub pull request creation from the command line?

Automate GitHub pull request creation by using the GitHub CLI to generate well-structured PRs from your commit history and project templates. This streamlines developer workflows by drafting context-rich descriptions and assigning reviewers directly from your branch.

How do I generate a pull request description using Linear issues and commit history?

Generate a pull request description by extracting context from linked Linear issues, commit messages, and code changes. The resulting PR body provides reviewers with comprehensive project context, ensuring a more efficient and informed code review process.

Do I need the GitHub CLI installed and authenticated to submit pull requests?

Yes, you need the GitHub CLI installed and authenticated to submit pull requests. The workflow relies on the GitHub CLI to interact with GitHub repositories, parse repository data with jq, and push the final PR creation commands.

Can I automatically assign reviewers when creating a GitHub PR?

Yes, you can automatically assign reviewers when creating a GitHub PR. The workflow prompts you for specified reviewers and adds them to the newly created pull request, facilitating an efficient and immediate code review assignment process.

What is the best way to structure a pull request for an efficient code review?

The best way to structure a pull request for an efficient code review is to synthesize commit history, Linear issue details, and PR templates into a comprehensive description. This provides reviewers with immediate context, reducing review friction and improving quality.

Why use GitHub CLI instead of the web interface for pull request automation?

Use the GitHub CLI instead of the web interface for pull request automation to seamlessly integrate PR creation into your developer workflow. This allows you to draft contextual descriptions from local commits and assign reviewers without leaving your terminal environment.