sidecar

Featured

Put this session into research-only mode — a secondary Claude sharing a working directory with another Claude that is actively editing code. No tracked-file edits and no git state mutations; reads, web/MCP research, session-scratchpad temp files, and GitHub issue creation are all allowed. Use at the start of a parallel planning/research/drafting session.

Code & Development 422 stars 49 forks Updated 4 weeks ago MIT

Install

View on GitHub

Quality Score: 88/100

Stars 20%
87
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Sidecar (research-only session) You are a **secondary session** sharing a working directory with another Claude Code session that is **actively editing code** in the same repository. Your job here is research, planning, theory, discussion, and drafting — **not** implementation. The other session owns the working tree; you must not step on it. Read-only operations, web/MCP research, and outward-facing actions that touch no local state are all fine. The only things that cause collisions are mutations to **shared local state**, so those are off-limits. ## The one rule **Do not mutate shared local state.** That state is exactly: tracked files in the working tree, and git's index/HEAD. Everything dangerous follows from those two; everything safe is safe because it touches neither. ### Forbidden - **Editing, creating, or deleting tracked files** in the repository (no `Edit`, `Write`, or `NotebookEdit` on anything under version control). Code, config, docs — all off-limits. - **Git state mutations:** `git add`, `git commit`, `git checkout` / `git switch`, `git branch`, `git stash`, `git reset`, `git restore`, `git rebase`, `git merge`, `git pull`. These corrupt whatever the other session is doing with the index, working tree, or HEAD. - **Creating branches or pull requests** (they require branch + push, i.e. git mutation). - **Installing dependencies, running formatters that rewrite files, or starting long-running servers** — these mutate `node_modules`, lockfiles, the tree,...

Details

Author
joshukraine
Repository
joshukraine/dotfiles
Created
12 years ago
Last Updated
4 weeks ago
Language
Shell
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

parallel-sessions-protocol

Coordinate any number of AI or human dev sessions working the same git repository in parallel — start-of-work registration (a draft PR is the shared board, with claim declarations), resource claiming (sequential numbers, file ownership), ledger-writes-only-at-merge-time, merge discipline (local merge preview, exclusive working directories, no `git add -A`), end-of-work registration (push-or-declare WIP, worktree cleanup, triggered write-backs), and a three-checkpoint awareness refresh. Use when multiple sessions / agents / worktrees develop one repo at the same time; when the user says 多会话并行, 并行轨道, 开工登记, 收工登记, 公告板, 会话撞车, 多个会话同时开发, coordinate parallel sessions, multiple Claude sessions on one repo, sessions keep colliding, track claims; when sequential resources (migration or decision numbers) or shared changelog/ledger docs keep colliding between branches; or when a session needs to know what other sessions are doing before acting. NOT for release/QA pipeline coordination through a dedicated controller lane,

1 Updated 2 days ago
laojin1900
AI & Automation Listed

collaborating-on-research

Use when working with a researcher on a long-running research project across many sessions — opening or closing a session, choosing a direction, method or scope, deciding whether to ask or act, planning what to run next, or writing up a result. Also when a published number failed to reproduce, a session ended with no record, a decision got made unilaterally, a write-up did not land, or the work has drifted from the research questions.

4 Updated 6 days ago
chgagne
DevOps & Infrastructure Listed

cloud-sessions

Working preferences and hard constraints for Claude Code Web (the browser and cloud environment at claude.ai/code, as opposed to the local CLI). Consult this whenever a session runs in that environment and something behaves differently from local — outbound network going through the egress proxy, GitHub access, installing tools, adding or scoping repositories, setting environment variables or secrets, a plugin or a repo's adopted conventions not being loaded, or a command that can't run in the sandbox and should be delegated to CI. Always-on preferences; they complement a repo's own CLAUDE.md rather than overriding it.

0 Updated yesterday
flungo