session-crosslink

What problem does it solve?

When an agent session runs outside the directory of the repositories it edits (for example, launched from a parent folder, a non-Entire repository, or a different repository entirely), the session is not automatically attached to the affected repositories' commit history, leaving a gap in provenance and context for future work.

Core Features & Use Cases

• Multi-strategy session ID resolution: Automatically finds the session ID from the current Entire-enabled directory, sibling Entire repositories, or agent runtime transcript files, no manual input required for common cases.
• Affected repo discovery: Identifies all relevant Entire-enabled repositories from user input, sibling repo scans, or the agent's edit history during the session.
• Preview-then-confirm safety: Shows a clear table of what actions will be taken per repository before any commits are amended, preventing accidental changes to the wrong commit.
• Use Case: If you are editing multiple microservice repositories from a shared parent folder, this skill automatically attaches your agent session to each service's latest commit so you retain full context of the changes later.

Quick Start

Ask your agent to attach your current cross-repo agent session to all affected Entire-enabled repositories after finishing work across multiple projects.