Agent skill · operations · vishalsachdev
start-session
Use when user says "let's get started", "where are we", or at beginning of a session. Reads project context from CLAUDE.md, checks git status and recent commits, and provides orientation for the session. Works across all repo types (code, research, mixed).
Why this skill is useful
Adds a comprehensive session initialization script that integrates project context, git status checks, and background process monitoring, which are not standard practices.
What it needs
About 4k tokens when loaded. Last updated 2026-08-01. 4 stars on the source repository.
What this skill does
Session Start Orient at the beginning of a work session. Execute these steps directly (do NOT spawn a subagent — you have the session context, a subagent does not). Steps 0. Read project instructions Check CLAUDE.md for ## Session Wrap-up, ## Deployment, sync commands, or similar sections. Note any sync/pull commands — you'll run them in Step 1. 1. Sync from remote If CLAUDE.md documents a sync or pull command (rsync, git pull, etc.), run it now. If nothing is documented, skip this step. 2. Detect repo type CLAUDE.md is already loaded into conversation context — don't re-read it. Detect repo type from type: declaration in CLAUDE.md or infer from contents (package.json = code, mostly .md = research). Only read agents.md or README.md if CLAUDE.md is missing or lacks project context. 3. Check git state After fetching, check if the current branch is behind the remote: If behind, note it in the summary so the user can decide whether to pull. Also list any remote-only branches (excluding main/master) if they exist: Check for forgotten stashes from previous sessions: If stashes exist, list them in the summary so the user can decide whether to pop or drop them. 3b. Check worktrees If the repo uses git worktrees (common for experiment frameworks): If multiple worktrees exist, list them in the summary. This surfaces sibling experiments or feature branches the user may have been working on. 4. Check for existing plans Look for files in .claude/plans/. If any exist, list them with a one-line summary. These may represent in-progress work from previous sessions. 5. Check for running background processes Flag any relevant background processes (pm2, nohup jobs, screen sessions, drip campaigns). These may be left over from a previous session or actively running. 5b. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vishalsachdev/start-session