session-crosslink

Attaches an agent session to each affected Entire-enabled repo's HEAD commit with preview-then-confirm.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/squidllee/skills --skill session-crosslink-squidllee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-crosslink
Source: https://github.com/squidllee/skills/tree/main/session-crosslink
Command: npx skills add https://github.com/squidllee/skills --skill session-crosslink-squidllee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent session runs outside the repo it edits — launched from a higher-level folder, a non-Entire directory, or one repo while editing another — none of the affected repos record the session, leaving commits without session linkage. ## Core Features & Use Cases - Session Resolution: Resolves the session id from entire session current --json, sibling repos, or runtime transcript directories (Claude Code, Codex). - Repo Discovery & Preview: Builds a candidate repo set from user input, sibling directories, and edit history, then computes a per-repo action table (add trailer, link existing, skip, or error) before making any change. - Confirmed Attach: Runs entire session attach per confirmed repo and reports a summary of attached, skipped, and failed repos. - Use Case: You ran a coding agent from a parent folder that touched three child repos; use this Skill to preview and attach the session to each repo's HEAD commit without amending the wrong commit. ## Quick Start Attach this agent session to every Entire-enabled repo it edited, showing me a preview table before amending any commits.

Frequently Asked Questions about session-crosslink

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

FAQPage Schema
How do I attach an agent session to a repo's HEAD commit?▼

Run `entire session attach <session-id> --agent <agent>` from inside the target repo; the CLI amends HEAD with an Entire-Checkpoint trailer. This Skill automates that across multiple repos with a preview table before any amend happens.

How do I find the session id when the session ran outside the repo?▼

Try `entire session current --json` first, then check an Entire-enabled sibling repo. If neither works, read the runtime transcript: Claude Code stores sessions at ~/.claude/projects/<encoded-cwd>/<session-id>.jsonl, and Codex under ~/.codex/sessions/.

Does entire session attach work if the repo already has a checkpoint trailer?▼

Yes. If HEAD already has an Entire-Checkpoint trailer, attach reuses that checkpoint id and adds the session to it. If the session is already tracked in the repo's state file, attach is a no-op and the row is skipped.

Why does entire session attach fail with 'Entire is disabled'?▼

The target repo opted out of Entire tracking, so attach refuses to run there. The Skill reports this and does not retry; enable Entire in that repo's settings if you want the session recorded.

What happens to open PRs after attaching a session?▼

Attach amends the HEAD commit, so the local branch diverges from its remote. If the branch has an open PR, force-push with `git push --force-with-lease` to update it.