skills.rest
oimiragieo
oimiragieoCOMMUNITY
Explore all skills by this author →
GitHub

context-bridge

Synchronize task state and metadata across Claude, Cursor, and Factory Droid sessions.

36|6|Updated Nov 2, 2025
Search Tags:#task management#productivity#workflow automation#integration#cross-platform#handoff#context sync
One-click install
npx skills add https://github.com/oimiragieo/LLM-RULES --skill context-bridge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-bridge
Source: https://github.com/oimiragieo/LLM-RULES/tree/main/.claude/skills/context-bridge
Command: npx skills add https://github.com/oimiragieo/LLM-RULES --skill context-bridge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Switching between different AI platforms (Claude, Cursor, Factory Droid) or external tools (Linear, GitHub, Slack) often results in lost context, requiring repetitive explanations and manual updates. This fragmentation wastes time and introduces inconsistencies. This Skill ensures your task state and metadata are synchronized, providing a continuous, uninterrupted workflow.

Core Features & Use Cases

  • Cross-Platform State Synchronization: Persists the current plan, active artifacts, and next steps across various AI sessions, allowing for smooth handoffs between tools.
  • External Tracker Updates: Automatically updates issue statuses, comments, or progress in integrated tools like Linear, GitHub, or Jira, keeping all stakeholders informed.
  • Use Case: You've started a feature implementation in Claude Code and need to continue in Cursor IDE. Ask the AI to "Sync this context to Cursor and update the Linear ticket". It will save your current progress, update the associated Linear ticket, and ensure Cursor picks up exactly where Claude left off, without any manual intervention.

Quick Start

Sync the current task context to Cursor and update the GitHub issue.

Frequently Asked Questions about context-bridge

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

FAQPage Schema
How do I sync task context between Claude, Cursor, and other AI platforms?▼

Context-bridge synchronizes task state and metadata across Claude, Cursor, and Factory Droid by persisting your current plan, artifacts, and next steps to .claude/context/state.json. When you hand off work between platforms, the receiving tool picks up exactly where you left off without manual re-explanation.

Can I automatically update Linear, Jira, or GitHub when switching between AI tools?▼

Yes. Context-bridge detects ticket IDs in your task state and automatically updates external tracker statuses, comments, and progress. When you sync context to a new platform, stakeholders stay informed through synchronized updates across all integrated tools.

What's the best way to prevent losing context when moving work between different development tools?▼

Cross-platform context synchronization persists your task metadata, plan, and artifacts to a central state file. Context-bridge reads existing state before writing, preserving history and ensuring continuity when you transition between Claude, Cursor, Factory Droid, or external trackers like Linear and GitHub.

Do I need to manually update tickets when I switch AI platforms mid-project?▼

No. Context-bridge handles it automatically. Specify the ticket ID once, then each time you sync context to a new platform, the Skill updates your external tracker status and notifies relevant channels without manual intervention.

How does context-bridge preserve task history across handoffs?▼

The Skill maintains a central state file (.claude/context/state.json) that reads existing context before each write, preserving your full task history. This ensures no information is lost when you hand off work between Claude, Cursor, Factory Droid, or external systems.

What happens if I don't have a ticket ID linked to my task?▼

Context-bridge still syncs your task state and metadata across platforms. It only attempts external tracker updates when a ticket ID is present. Without a ticket ID, state synchronization and cross-platform handoffs work normally.

Related Skills

Explore More Product & Management Skills→
CoorpAcademyCoorpAcademy
1

jira-ticket

Parse Jira tickets to extract requirements and generate developer summaries.

Official
Advanced
automatedigitalautomatedigital
1

tasker

Automate ticket lifecycle from ideation to merged pull request across ticket trackers and GitHub.

Official
Advanced
jieni777jieni777
1

composio

Connect Slack, Jira, Linear, GitHub and 100+ platforms for cross-tool workflows.

Community
Advanced
Dev10x-GuruDev10x-Guru
7

Dev10x:slack-review-request

Send Slack review notifications for GitHub Pull Requests.

Official
Advanced