playbooks

home / skills / thebushidocollective / han / issue

issue skill

/plugins/services/linear/skills/issue

This skill retrieves and presents detailed Linear issue information, improving issue visibility and tracking for quick context and decision making.

npx playbooks add skill thebushidocollective/han --skill issue

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.1 KB
---
name: issue
description: Get detailed information about a specific Linear issue
---

# issue

## Name

linear:issue - Get detailed information about a specific Linear issue

## Synopsis

```
/issue [arguments]
```

## Description

Get detailed information about a specific Linear issue

## Implementation

Retrieve and display comprehensive details for a Linear issue.

**Usage**: `/issue ENG-123`

Use the Linear MCP tool `linear_get_issue` to fetch full issue details.

Display in sections:

## 📋 Issue: ENG-123

**Title**: {title}
**Status**: {state name}
**Assignee**: {assignee}
**Priority**: {priority}
**Created**: {created date}
**Updated**: {updated date}
**Cycle**: {cycle/sprint if in one}
**Project**: {project if assigned}

## Description

{full description with formatting}

## Acceptance Criteria

{Extract and highlight any acceptance criteria or requirements}
{Parse checklist items if present}

## Recent Activity

{Show last 3 comments with author and date}

## Related Issues

{Show linked issues with relationship}

Provide the direct link to the issue at the end.

Overview

This skill fetches and presents detailed information for a specific Linear issue. It formats core metadata, description, acceptance criteria, recent activity, related issues, and provides a direct link to the issue. Use the command with the Linear issue key (for example: /issue ENG-123).

How this skill works

The skill calls the Linear MCP endpoint to retrieve full issue details using the supplied issue key. It extracts and formats metadata (title, status, assignee, priority, dates, cycle, project), the full rich-text description, any checklist or acceptance criteria, the last three comments, and linked issues. Finally, it returns a structured, human-readable summary with a direct link to the issue.

When to use it

  • You need a concise, shareable snapshot of an issue during standups or triage.
  • Preparing context for code reviews, pull requests, or design discussions.
  • Verifying acceptance criteria and checklist items before QA or release.
  • Investigating recent activity or comments on a ticket.
  • Linking related issues to understand dependencies and blockers.

Best practices

  • Provide the exact Linear issue key to avoid ambiguous results.
  • Use the returned direct link to open the issue for full history or edits.
  • Treat the description as authoritative and check formatted checklists for acceptance steps.
  • Cross-reference related issues before changing status or priorities.
  • Use the last three comments to quickly gauge recent decisions or blockers.

Example use cases

  • During a sprint planning meeting, call /issue ENG-123 to present the ticket and acceptance criteria.
  • Before merging a feature branch, verify the issue’s acceptance checklist and recent QA comments.
  • When unblocking work, fetch the issue to find linked dependencies and assignees.
  • Triage incoming bug reports by pulling full issue context and recent discussion.

FAQ

What input does the skill require?

You must provide a valid Linear issue key (for example: ENG-123).

Does it show comments and linked issues?

Yes. It surfaces the last three comments with author and date and lists linked issues and their relationships.