linear-issue-delivery

Solid

Keep a Linear issue aligned with implementation evidence, acceptance criteria, code review, and deployment state while avoiding premature completion claims.

Code & Development 6,691 stars 1288 forks Updated yesterday NOASSERTION

Install

View on GitHub

Quality Score: 84/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
29
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Linear Issue Delivery 1. Read the issue, linked work, acceptance criteria, and current status. 2. Inspect the local or remote implementation evidence supplied by the user. 3. Report gaps between the issue and the actual change before editing either side. 4. Add concise evidence or update status only when the requested milestone is genuinely reached. 5. Preserve links to pull requests, tests, releases, or follow-up issues when available. Do not mark work done based only on a local edit. Distinguish local implementation, pushed code, merged code, and deployed behavior.

Details

Author
Devin-AXIS
Repository
Devin-AXIS/iPolloWork
Created
1 years ago
Last Updated
yesterday
Language
TypeScript
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category