checkout

Execute Linear tasks end-to-end with branching, implementation, and local validation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maxbeaudoin/productflash --skill checkout-maxbeaudoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: checkout
Source: https://github.com/maxbeaudoin/productflash/tree/main/.claude/skills/checkout
Command: npx skills add https://github.com/maxbeaudoin/productflash --skill checkout-maxbeaudoin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual, error-prone process of locating the right Linear issue and carrying it through a safe local implementation and validation workflow before opening a PR.

Core Features & Use Cases

  • Linear issue resolution with guardrails: Selects the highest-priority unblocked issue (or loads an explicit Linear ID/URL) while avoiding tasks blocked by incomplete dependencies and skipping tasks assigned to others.
  • Branching + execution workflow: Creates a fresh branch from up-to-date main, loads the issue context, moves it to In Progress, executes the work, and stops before PR creation.
  • Local validation and handoff: Runs local tests and dev checks (including browser + database verification where relevant), captures UI screenshots to /tmp when applicable, and reports back for /open-pr.

Quick Start

Run /checkout to automatically pick the highest-priority unblocked ProductFlash issue and execute it end-to-end locally up to the PR handoff stage.

Frequently Asked Questions about checkout

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

FAQPage Schema
How do I automate Linear task execution from issue resolution to local validation?

Automating Linear task execution requires resolving the correct unblocked issue, branching from updated main, implementing changes, and validating locally with tests, dev server checks, and database queries before PR handoff.

How does Linear MCP integration work with git branching for product development?

Linear MCP integration works with git branching by listing and fetching Linear issues, moving the selected unblocked issue to In Progress, creating a fresh branch from up-to-date main, and saving issue state during incremental commits referencing the Linear ID.

Do I need the Linear MCP to branch from updated main and execute tasks?

Yes, Linear MCP calls are required to list, fetch, and save issue state. The workflow resolves the correct issue, avoids tasks blocked by dependencies or assigned to others, and traces changes to Linear IDs during git branching and incremental commits.

What is the best way to guard against blocked tasks and other assignees when executing Linear issues locally?

The best way to guard against blocked tasks is selecting the highest-priority unblocked issue while skipping tasks with incomplete dependencies or assignments to others, then running local validation steps including tests, browser checks, and database API verification before PR handoff.

Does the local validation workflow capture UI screenshots when implementing Linear changes?

Yes, the local validation workflow captures UI screenshots to /tmp when applicable. It runs local tests and dev checks, including browser and database verification where relevant, to confirm UI impact before reporting back for PR handoff.

Why does the execution workflow stop before PR creation after local validation?

The execution workflow stops before PR creation to provide a local validation and handoff stage. It runs tests, captures UI screenshots to /tmp, verifies database and API changes, and reports back so the /open-pr command can handle the final PR submission.