pull-request

Create a pull request for a monorepo sibling and link it to a Linear issue.

68|18|Updated Aug 12, 2025
One-click install
npx skills add https://github.com/DayMoonDevelopment/post-for-me --skill pull-request-daymoondevelopment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pull-request
Source: https://github.com/DayMoonDevelopment/post-for-me/tree/main/.agents/skills/pull-request
Command: npx skills add https://github.com/DayMoonDevelopment/post-for-me --skill pull-request-daymoondevelopment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow streamlines creating high-quality pull requests for the post-for-me monorepo and ensures each PR is linked to its corresponding Linear issue, reducing manual tracking and context-switching.

Core Features & Use Cases

  • Creates and opens PRs that touch a single sibling in the monorepo, keeping changes scoped and clear.
  • Enforces branch naming conventions (feat/, fix/, chore/) and supplies a PR body template with automatic Linear linkage.
  • Updates Linear issues via the MCP, attaching the PR URL and moving the issue to In Review to reflect progress.

Quick Start

Create a feature branch off main (e.g., feat/new-feature), open a pull request for the target sibling, and attach the PR to the Linear issue.

Frequently Asked Questions about pull-request

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

FAQPage Schema
How do I automate opening pull requests and link them to Linear issues?

Automating pull requests linked to Linear issues involves creating a feature branch off main, opening a PR for a single monorepo sibling, and attaching the PR URL to the Linear issue via MCP. This moves the issue to In Review automatically.

What's the best way to scope a pull request in a monorepo?

Scoping a pull request in a monorepo is best done by targeting a single sibling directory. This keeps changes isolated, ensures the PR body remains clear using the provided template, and maintains focused branch naming conventions.

How does branch naming convention enforcement work for GitHub PRs?

Branch naming convention enforcement for GitHub PRs requires prefixes like feat/, fix/, or chore/ before opening a pull request. This ensures branches are opened off main with an appropriately prefixed name matching the change type.

Can I use this to attach a PR URL to a Linear issue via MCP?

Yes, you can attach a PR URL to a Linear issue via the MCP. The workflow updates the corresponding Linear issue by attaching the pull request URL and moving the issue status to In Review to reflect progress.

Do I need a specific branch naming format to link GitHub pull requests to Linear?

You need a branch naming format using feat/, fix/, or chore/ prefixes to properly link GitHub pull requests to Linear. The PR must be opened off main with the correctly prefixed branch to ensure tracking and automatic status updates.

Why should a pull request target a single sibling in a monorepo?

A pull request should target a single sibling in a monorepo to keep changes scoped and clear. This isolation prevents unrelated modifications from mixing, ensuring the PR body template remains focused and the Linear issue tracking stays accurate.