Stats
Actions
Tags
From linear
Starts work on Linear issue: fetches details, displays title/status/assignee/acceptance criteria, transitions to In Progress, adds comment, optionally assigns to user. Use via /start [id].
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear:startThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
linear:start - Start work on a Linear issue (transition to In Progress)
linear:start - Start work on a Linear issue (transition to In Progress)
/start [arguments]
Start work on a Linear issue (transition to In Progress)
Start work on a Linear issue by transitioning it to "In Progress" and displaying acceptance criteria.
Usage: /start ENG-123
Steps:
linear_get_issue to fetch issue detailslinear_update_issue_state to transition to "In Progress"linear_add_comment to add: "Starting work on this issue"linear_update_issue to assign to current user if unassignedDisplay Format:
▶️ Starting work on ENG-123
Title: {issue title}
Status: {old status} → In Progress
Assignee: {assignee}
📋 Acceptance Criteria:
{list all acceptance criteria}
Link: {issue URL}
If issue is already In Progress, just display current status and acceptance criteria without transitioning.
npx claudepluginhub thebushidocollective/han --plugin linearTransitions Jira ticket to In Progress, displays summary/status/assignee and acceptance criteria checklist, adds starting comment. Invoke via /start TICKET-ID.
Moves a Linear issue to a different workflow state by resolving the state name from a cached catalogue. Requires explicit user confirmation before applying the transition.
Validates Linear issue acceptance criteria via user prompts and marks complete with comment if all met; lists incompletes otherwise. Invoke via /complete ISSUE-ID.