start-session

Gather branch and workspace context into a structured briefing before development.

37|6|Updated Oct 10, 2025
One-click install
npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill start-session-carrotwaxr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-session
Source: https://github.com/carrotwaxr/peek-stash-browser/tree/main/.claude/skills/start-session
Command: npx skills add https://github.com/carrotwaxr/peek-stash-browser --skill start-session-carrotwaxr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often begin work on a branch or return to a codebase without an organized view of the current branch state, uncommitted changes, related plan documents, or recent activity; this Skill gathers that context and presents a concise briefing so work starts with clarity and fewer mistakes.

Core Features & Use Cases

  • Branch and Workspace Inspection: Detects current branch, uncommitted changes, divergence from main, recent commits, and stashes to reveal the true starting state.
  • Context Aggregation: Locates and summarizes plan documents, related GitHub issues, and previous session notes; queries a memory service for prior decisions and gotchas.
  • Health Checks and Safeguards: Runs quick checks for behind/main status and uncommitted work to prevent accidental overwrites.
  • Structured Briefing & Confirmation: Produces a formatted session briefing with suggested next steps and asks for human confirmation before any code changes.
  • Use Case: On a feature branch, use this Skill to confirm what was left incomplete, surface relevant plans or tickets, and decide the immediate next coding action.

Quick Start

Run the start-session skill to collect branch context, uncommitted changes, plan documents, recent commits, and present a structured briefing for confirmation before editing code.

Frequently Asked Questions about start-session

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

FAQPage Schema
How do I gather git branch context and uncommitted changes before starting a coding session?

A session briefing skill aggregates uncommitted changes, recent commits, and plan documents into a structured summary. It queries memory services for prior decisions and presents suggested next steps for confirmation before editing code.

What is the best way to orient a resumed feature branch and find related plan documents?

To orient a resumed feature branch, query a memory service for previous session notes and git activity. This surfaces related GitHub issues and prior gotchas, revealing the true starting state before development resumes.

Does this developer workflow onboarding tool check for behind main status and stashes?

Yes, the developer workflow onboarding tool runs health checks for behind main status and uncommitted work. It detects current branch stashes and divergence to prevent accidental overwrites before starting development.

Can I use context gathering to summarize uncommitted changes and recent git activity?

Yes, you can use context gathering to summarize uncommitted changes and recent git activity. The skill locates plan documents, queries memory services for prior decisions, and produces a formatted session briefing with suggested next steps.

How do I prevent accidental overwrites when resuming work on a bug fix branch?

To prevent accidental overwrites when resuming work on a bug fix branch, run health checks for behind main status and uncommitted changes. The skill asks for human confirmation before applying any code changes.

Why does my session briefing include suggested next steps before editing code?

Your session briefing includes suggested next steps to ensure work starts with clarity and fewer mistakes. By aggregating branch status, related issues, and prior decisions from memory services, the skill provides a structured plan for confirmation.