skills.rest
everruns
everrunsOFFICIAL
Explore all skills by this author →
Website𝕏@everrunshqGitHub

process-issues

Select Linear OSS issues and ship one PR per issue via /ship.

42|1|Updated Dec 14, 2025
Search Tags:#automation#workflow#linear#issues#process#pull-request#oss
One-click install
npx skills add https://github.com/everruns/everruns --skill process-issues-everruns
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: process-issues
Source: https://github.com/everruns/everruns/tree/main/.agents/skills/process-issues
Command: npx skills add https://github.com/everruns/everruns --skill process-issues-everruns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines open Linear issue management by ensuring every issue is addressed with a focused, single-PR shipping workflow.

Core Features & Use Cases

  • One-PR-per-issue policy: guarantees isolated changes per issue and clear traceability.
  • End-to-end shipping via /ship: delegates PR creation, validation, CI, and merge to the dedicated shipping workflow.
  • Ownership checks and prioritization: evaluates Linear ownership, blocks stale handoffs, and prioritizes high-value work from the OSS backlog.
  • Operational guidance: provides a deterministic, auditable process for tracking progress from pickup to Done.

Quick Start

Process open Linear issues by selecting the highest-value item and shipping one PR per issue using the /ship workflow.

Frequently Asked Questions about process-issues

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

FAQPage Schema
How do I automate Linear OSS issue management to ship one PR per issue?▼

Automating Linear OSS issue management involves selecting high-value backlog items and shipping one PR per issue using the /ship workflow. This enforces ownership checks, isolated changes, and end-to-end PR lifecycle traceability from pickup to Done.

What is the best way to enforce a strict one-PR-per-issue workflow for backlog grooming?▼

The best way to enforce a one-PR-per-issue workflow is to apply a deterministic process that delegates PR creation, validation, and CI to a dedicated shipping workflow. This ensures isolated changes and operational traceability for OSS backlog grooming.

How does the /ship workflow handle pull request creation and CI validation?▼

The /ship workflow handles pull request creation by delegating PR creation, validation, CI, and merge operations to a dedicated shipping workflow. This guarantees every Linear issue is addressed with a focused, single-PR lifecycle.

Can I automate bug triage and feature delivery for issues tracked in Linear?▼

Yes, you can automate bug triage and feature delivery for issues tracked in Linear. The process evaluates Linear ownership, blocks stale handoffs, and prioritizes high-value work from the OSS backlog to ensure deterministic delivery.

Does enforcing a single PR per issue prevent stale handoffs in OSS workflows?▼

Enforcing a single PR per issue prevents stale handoffs by applying strict ownership checks and prioritizing high-value work. This deterministic, auditable process tracks progress from pickup to Done, ensuring clear traceability.

Related Skills

Explore More Software Engineering Skills→
GainInsightDevGainInsightDev

af-plan-work-cycles

Plan weekly work cycles and prioritize backlogs using Linear issue states and estimates.

Official
Advanced
blackplume233blackplume233
12

pr-handler

Automate the five-phase PR gatekeeping workflow for Draft PRs.

Community
Advanced
AnveioAnveio
1

task-pull-request

Automate GitHub pull request creation, reviews, feedback, and merges via gh CLI.

Community
Intermediate
hmzainjamilhmzainjamil
1

Jira Automation

Automate Jira issue management, sprint planning, and workflow transitions.

Community
Advanced