linear-issue-to-prlisted

Takes a Linear issue identifier (e.g. ENG-42) and carries it end to end in the current git repo - fetches the issue and its comments, creates or switches to the issue branch, implements the change, commits, pushes and opens a pull request (never merges). Use it whenever the user gives a Linear issue ID and wants it worked on, e.g. "get issue ENG-42", "work on ENG-42", "implement DBO-1104", "resuelve la issue ENG-42", "trabaja en ENG-42", or names a project together with an issue ID. Do not use it when the user only asks about an issue's status, wants to create or plan issues, or wants a summary without code changes.
mbarradev-debug/linear-issue-to-pr · ★ 1 · Code & Development · score 80

Install: claude install-skill mbarradev-debug/linear-issue-to-pr

# Linear issue → working pull request Turn a Linear issue into a pushed branch and an open PR, in one pass. The user invokes this skill because the issue in Linear already *is* the specification. What they want back is the work, not a retelling of the ticket. That idea drives most of the rules below. ## How to behave **Execute, don't re-diagnose.** A trigger like "get issue ENG-42" means "do the work". Fetch, classify, plan and implement in the same turn. Do not stop after fetching to summarize the issue, and do not open with a clarifying question: the title, description, acceptance criteria and comments are the spec. Pause only for the abort conditions listed in [Stop conditions](#stop-conditions). **Keep the plan internal.** You will build a working plan (step 4). It is for you. Do not print it, paraphrase it, or narrate "here is my understanding of the issue" before starting. The user already has all of that in Linear, and repeating it costs their time and tokens. The only thing shown before work begins is the one-line status line from step 5. Explanations belong in the final report. **Keep git history human.** Commits, PR titles, PR bodies and branch names made under this workflow carry no AI attribution: no `Co-Authored-By: Claude` trailer, no session link, no "Generated with" footer. The commit author is the human developer. This is the explicit choice of the user who installed this skill, so it takes precedence over default attribution templates your environment