linear-issue-delivery

Aligns Linear issues with implementation evidence, acceptance criteria, and deployment state.

5.3k|976|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill linear-issue-delivery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear-issue-delivery
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/linear/skills/linear-issue-delivery
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill linear-issue-delivery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often mark Linear issues complete based only on local edits, creating a gap between issue status and actual delivery. This Skill keeps issue tracking honest by verifying implementation evidence, code review state, and deployment before any status change.

Core Features & Use Cases

  • Evidence-Based Status Updates: Reads the issue, linked work, and acceptance criteria, then compares them against actual implementation evidence before editing anything.
  • Gap Reporting: Reports discrepancies between the issue description and the real change before modifying either side.
  • Delivery Stage Distinction: Distinguishes local implementation, pushed code, merged code, and deployed behavior to prevent premature completion claims.
  • Use Case: An engineer finishes a feature branch and asks to close the Linear issue. The Skill checks whether the pull request is merged and deployed, preserves links to the PR and tests, and only updates the issue status when the requested milestone is genuinely reached.

Quick Start

Ask the assistant to review Linear issue ENG-123 against the current pull request and update its status only if the acceptance criteria are actually met.

Frequently Asked Questions about linear-issue-delivery

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

FAQPage Schema
How do I keep Linear issues in sync with actual code delivery?

Read the issue, its linked work, and acceptance criteria, then compare them against concrete implementation evidence such as pull requests and deployments. Update the issue status only when the requested milestone is genuinely reached, not when code is merely written locally.

How to avoid closing Linear issues prematurely?

Distinguish between local implementation, pushed code, merged code, and deployed behavior before marking work done. Report gaps between the issue and the actual change first, and only add evidence or update status when the milestone is verified.

Can this Skill update Linear issue status automatically?

It adds concise evidence or updates status only when the requested milestone is genuinely reached based on supplied implementation evidence. It preserves links to pull requests, tests, releases, or follow-up issues when available.

What evidence is needed before marking a Linear issue done?

Acceptable evidence includes merged pull requests, passing tests, releases, and confirmed deployed behavior. A local edit alone is never sufficient grounds for marking work complete.

When should I not update a Linear issue status?

Do not update status when implementation evidence is missing, when code exists only locally, or when acceptance criteria remain unmet. Instead, report the gaps between the issue and the actual change before editing either side.