sideload

Load CLAUDE.md, rules, and crew context from a sibling repository into the current Claude Code session.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/weside-ai/claude-code-plugin --skill sideload-weside-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sideload
Source: https://github.com/weside-ai/claude-code-plugin/tree/main/we/skills/sideload
Command: npx skills add https://github.com/weside-ai/claude-code-plugin --skill sideload-weside-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a means to load essential context from another repository into the current session without the need to switch, enabling seamless cross-repo work.

Core Features & Use Cases

  • Cross-Repository Context Loading: Load CLAUDE.md, rules, and crew information from a neighbor repository into the current session.
  • Efficient Work Transition: Work on another repository within the same Claude Code session for faster transitions.
  • Use Case: If you need to understand and work on the context of a different repository within the current session, use /we:sideload to quickly import the necessary information.

Quick Start

Load context for a sibling repository by typing /we:sideload backend-repo.

Frequently Asked Questions about sideload

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

FAQPage Schema
How do I load context from another repository into my current Claude Code session?

To load context from another repository, use the sideload command to import essential files like CLAUDE.md and rules, enabling seamless cross-repo work without switching your active session.

Can I work on a sibling repository without switching my active session?

Yes, you can work on a sibling repository without switching your active session by loading its essential context directly, allowing for efficient work transitions and uninterrupted collaborative coding.

Do I need a configuration file to map contexts for cross-repo work?

Yes, cross-repo context loading requires a `.weside/config.json` file for context mapping to successfully integrate neighbor repository information like crew details into the current session.

What specific repository files can be shared when working across multiple repositories?

When working across multiple repositories, you can load essential context files including CLAUDE.md, rules, and crew information to ensure the main agent has the necessary operational context.

Why does loading context from a neighbor repository fail during collaborative coding?

Loading context from a neighbor repository fails during collaborative coding if the required `.weside/config.json` mapping file is missing or incorrectly configured for the target repository context.

What is the best way to quickly integrate context from a different repository?

The best way to quickly integrate context from a different repository is to use the dedicated context loading command, which imports CLAUDE.md and rules directly into the current session for immediate cross-repo work.