jinn-unblock

Diagnose and resolve blocked Linear issues via Linear MCP.

1|Updated Sep 2, 2019
One-click install
npx skills add https://github.com/hackefeller/hominem --skill jinn-unblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jinn-unblock
Source: https://github.com/hackefeller/hominem/tree/main/.claude/skills/jinn-unblock
Command: npx skills add https://github.com/hackefeller/hominem --skill jinn-unblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve blocked Linear issues by diagnosing blockers, classifying them, and applying appropriate resolutions, updating Linear accordingly.

Core Features & Use Cases

  • Diagnose the blocker on a Linear issue and classify as stale dependency, missing information, technical dependency, scope conflict, or external dependency
  • Apply the corresponding resolution path (close or defer dependencies, clarify information, split scope, or leave blocked with unblocking conditions) and update the parent issue
  • Generate an unblock report and leave a documented trail for audit and future prevention
  • Integrate with Linear MCP workflow and jinn CLI tools to automate status updates and comments

Quick Start

Run jinn-unblock on a blocked Linear issue to classify the blocker and apply the appropriate resolution.

Frequently Asked Questions about jinn-unblock

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

FAQPage Schema
How do I automatically diagnose and unblock blocked Linear issues?

Automatically diagnose and unblock blocked Linear issues by classifying blockers as stale dependencies, missing information, or scope conflicts, then applying resolution paths and updating the parent issue status via Linear MCP.

What types of blockers can be resolved for Linear issue management?

Linear issue blockers are classified as missing information, stale dependencies, technical dependencies, scope conflicts, or external dependencies, with each type triggering a corresponding resolution path like scope splitting or dependency deferral.

Do I need a Linear MCP server configured to classify and resolve issue blockers?

Yes, resolving issue blockers requires a configured Linear MCP server, the jinn CLI, and access to the blocked issue to automate status updates, classify the blocker, and leave a documented comment trail.

How do I resolve scope conflicts and missing information on blocked Linear workflow tickets?

Resolve scope conflicts by splitting the issue scope, and clarify missing information by requesting details, then update the parent Linear issue and leave an unblock report comment trail for audit and prevention.

What is the best way to handle stale and external dependencies blocking Linear tickets?

Handle stale and external dependencies by closing or deferring them, leaving the issue blocked with unblocking conditions, or applying the appropriate resolution path, then updating Linear with a documented audit trail.