jinn-apply

Automate Linear issue selection, claim, and completion workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the end-to-end execution of Linear-based work by guiding one issue at a time, handling blockers, and ensuring consistent status updates to stakeholders.

Core Features & Use Cases

  • Single-issue execution loop that selects, claims, and closes one Linear task at a time.
  • Blocker detection and proper surface of dependencies to prevent context-switching.
  • Automatic status synchronization with Linear MCP to reflect progress and completion, plus concise post-work summaries.

Quick Start

Tell the AI to start the Linear work workflow on the next available unblocked issue.

Frequently Asked Questions about jinn-apply

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

FAQPage Schema
How do I automate Linear issue management from claim to completion?

You can automate Linear issue management using a single-issue execution loop that selects, claims, and closes one task at a time. This coordinates issue selection and status updates via Linear MCP to ensure consistent progress tracking.

What is the best way to handle blockers in Linear workflow automation?

The best way to handle blockers in Linear workflow automation is through dependency detection that surfaces blockers before task selection. This prevents context-switching by ensuring only unblocked issues enter the execution loop.

Does this Linear workflow automation enforce single In Progress work?

Yes, this Linear workflow automation enforces single In Progress work through built-in guardrails. It ensures only one issue is actively worked at a time and verifies completion before closing the task.

How do I start the Linear work workflow on unblocked issues?

To start the Linear work workflow on unblocked issues, instruct the AI to begin the workflow on the next available unblocked issue. The system then automatically selects, claims, and executes the task while synchronizing status via Linear MCP.

Can I use Linear MCP to manage sub-issues and status updates?

Yes, you can use Linear MCP to manage sub-issues and status updates. The workflow automatically synchronizes progress and completion status with Linear MCP, and generates concise post-work summaries for stakeholders.

Why does Linear issue execution require verified completion before closing?

Linear issue execution requires verified completion before closing as a guardrail to ensure work quality and consistency. This prevents premature closure and maintains reliable status synchronization with stakeholders via Linear MCP.