grey-haven-linear-workflow

Automate Linear issue creation, branch naming, and PR integration with Git workflows.

29|4|Updated Aug 10, 2025
One-click install
npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-linear-workflow
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: grey-haven-linear-workflow
Source: https://github.com/greyhaven-ai/claude-code-config/tree/main/grey-haven-plugins/linear/skills/linear-workflow
Command: npx skills add https://github.com/greyhaven-ai/claude-code-config --skill grey-haven-linear-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill eliminates the chaos of disconnected project management by automating Linear issue tracking, Git workflows, and PR processes, ensuring consistent quality and saving hours of manual coordination.

Core Features & Use Cases

  • Issue Management: Create well-structured Linear issues with templates for features, bugs, and migrations.
  • Git Integration: Automatically sync branch names, commit messages, and PRs with Linear issue IDs.
  • Use Case: When starting a new feature, use this Skill to create a properly formatted Linear issue, generate the correct branch name, and ensure all commits and PRs automatically update issue status.

Quick Start

Create a new Linear issue for adding user authentication following the feature template structure.

Frequently Asked Questions about grey-haven-linear-workflow

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

FAQPage Schema
How do I automate Linear issues and Git workflows together?โ–ผ

Automate Linear issues and Git workflows by syncing issue IDs directly to branch names, commit messages, and pull requests. This Skill creates structured Linear issues with templates, generates compliant branch names automatically, and ensures commits and PRs update issue status without manual coordination.

Can I use Linear issue templates with standardized branch naming conventions?โ–ผ

Yes. This Skill enforces issue templates for features, bugs, and migrations while automatically generating branch names from Linear issue IDs. Branch naming follows conventions tied to issue metadata, keeping your workflow consistent across team members and environments.

How do I link pull requests to Linear issues automatically?โ–ผ

Pull requests link to Linear issues automatically by embedding issue IDs in commit messages and PR descriptions. The Skill structures PR descriptions to recognize Linear keywords, updating issue status as PRs move through your workflow without manual intervention.

What's the best way to maintain multi-tenant isolation in automated workflows?โ–ผ

Maintain multi-tenant isolation by configuring tenant_id handling, RLS policies, and Doppler secrets management within the workflow. This Skill performs tenant-aware checks across issue creation, branching, and PR integration, ensuring data stays isolated per environment.

Do I need a specific Git commit message format to use this workflow?โ–ผ

Yes. This Skill requires commit messages integrated with Linear issue IDs to track work consistently. The format aligns commits with issues automatically, enabling PR descriptions and issue status updates to function end-to-end across your development cycle.

When should I not use automated issue-to-PR workflows?โ–ผ

Avoid this approach if your team doesn't create Linear issues before starting work or if your repository lacks standardized commit and branch naming conventions. The Skill requires discipline around issue creation and consistent formatting to function effectively.