Resolve missing session provenance for code changes across Entire-enabled repositories.
npx skills add https://github.com/entireio/skills --skill session-crosslink
Please help me install this Agent Skill. Skill: session-crosslink Source: https://github.com/entireio/skills/tree/main/skills/session-crosslink Command: npx skills add https://github.com/entireio/skills --skill session-crosslink
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.
Ask your agent to attach your current cross-repo agent session to all affected Entire-enabled repositories after finishing work across multiple projects.
High-intent search queries and answers about installing and using this skill.
To attach an agent session to a repository from a parent directory, you can use a session linking tool that automatically resolves the session ID and attaches it to the affected repo's HEAD commit. This ensures commit provenance is maintained for cross-repo workflows.
Agent sessions do not link to commit history across multiple repositories because they are launched outside the target Entire-enabled repository's directory. This leaves a gap in provenance, requiring a session attachment tool to link the context to each affected repo.
Yes, you can automatically discover affected Entire-enabled repositories by scanning user input, sibling repositories, or the agent's edit history during the session. This identifies all relevant repos requiring session context attachment to their latest commits.
You can safely link agent sessions to commits using a preview-then-confirm safety mechanism. This approach displays a clear table of proposed actions per repository before any commits are amended, preventing accidental changes to the wrong commit history.
When attaching a session to an uninitialized repo or an already linked commit, the multi-strategy resolution process includes specific error handling for these edge cases. It safely manages uninitialized repos, existing links, and disabled Entire integrations without breaking.
kwam1naScaffold agent-ready repositories with onboarding docs, validation maps, and CI wiring.
DasBluEyedDevilCoordinate cross-repo Daem0n-MCP memory initialization and consolidation.
NagasakaHCoordinate multi-repository commits across parent and submodules with staged verification.
simonwjacksonEmit structured JSON metadata for session files across Claude Code, Codex, and Cursor.
