github-lanes-bridge

Import GitHub issues into Lanes for local Claude Code execution.

253|16|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/lanes-sh/app --skill github-lanes-bridge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-lanes-bridge
Source: https://github.com/lanes-sh/app/tree/main/plugins/lanes-desktop/skills/github-lanes-bridge
Command: npx skills add https://github.com/lanes-sh/app --skill github-lanes-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill facilitates the integration of GitHub issues with Lanes, enabling local Claude Code execution, batch-spawning sessions, and posting results back to GitHub.

Core Features & Use Cases

  • Bridging GitHub and Lanes: Import GitHub issues into Lanes for local Claude Code execution.
  • Batch-Spawning Sessions: Create multiple Claude sessions per GitHub ticket.
  • Decomposition: Break down a single GitHub issue into multiple Lanes sub-issues with dependencies.
  • Round-Trip: Post session results (PR links, comments, follow-up issues) back to GitHub.
  • Use Case: When you need to execute Claude Code locally on GitHub issues, track progress, and report back to GitHub.

Quick Start

Use the github-lanes-bridge skill to import a GitHub issue into Lanes for local Claude Code execution by saying "import this GitHub issue into Lanes".

Frequently Asked Questions about github-lanes-bridge

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

FAQPage Schema
How do I execute Claude Code locally on GitHub issues?

To execute Claude Code locally on GitHub issues, use a bridge to import them into Lanes, spawn local sessions, and post results like PR links back to GitHub automatically.

Can I break down a single GitHub issue into multiple Lanes sub-issues?

Yes, you can decompose a single GitHub issue into multiple Lanes sub-issues, automatically generating dependencies and batch-spawning individual Claude Code sessions for each sub-task.

Do I need GitHub and Lanes MCP connected to use the github-lanes-bridge?

Yes, you must have both GitHub and Lanes MCP connected, as the bridge requires these integrations to import issues, execute local code, and report round-trip results back.

What is the best way to report Claude Code execution results back to GitHub?

The best way to report results back to GitHub is using a round-trip bridge that posts session outputs, including PR links, comments, and follow-up issues, directly from Lanes.

How do I batch-spawn multiple Claude sessions per GitHub ticket?

You can batch-spawn multiple Claude sessions per GitHub ticket by importing the issue into Lanes, which handles creating and managing the concurrent local execution environments.