Skip to content
Back to skills

Session Startup

ASecurity

Auto-run at the start of every Claude Code session. Loads project context, checks for active tasks, connects MCP servers, and suggests the right skill for the current workflow phase. This is the "boot sequence" that ensures every session starts with maximum context and minimum waste. Trigger: Run at session start or when switching projects.

  • 6 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added May 27, 2026
developmentgobashgit

Works with

  • claude code
  • mcp

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add KevinZai/commander --skill session-startup --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Session Startup?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Session Startup
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/kevinzai-session-startup/badge)](https://www.skillsdirectory.com/skills/kevinzai-session-startup)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: session-startup
description: |
  Auto-run at the start of every Claude Code session. Loads project context,
  checks for active tasks, connects MCP servers, and suggests the right skill
  for the current workflow phase. This is the "boot sequence" that ensures
  every session starts with maximum context and minimum waste.
  Trigger: Run at session start or when switching projects.
allowed-tools:
  - Bash
  - Read
---

# Session Startup

## Boot Sequence (run in order)

### 1. Load Context
```bash
# Read project CLAUDE.md
[ -f CLAUDE.md ] && echo "πŸ“‹ Project CLAUDE.md found" || echo "⚠️ No project CLAUDE.md β€” consider /project init"

# Read active tasks
[ -f tasks/todo.md ] && echo "πŸ“ Active tasks:" && grep -c "^\- \[ \]" tasks/todo.md | xargs -I{} echo "  {} incomplete items" || echo "πŸ“ No tasks/todo.md"

# Read recent lessons
[ -f tasks/lessons.md ] && echo "πŸ“– Lessons file found" || true
```

### 2. Check Git State
```bash
branch=$(git branch --show-current 2>/dev/null || echo "not a git repo")
dirty=$(git status -s 2>/dev/null | wc -l | tr -d ' ')
echo "🌿 Branch: $branch | Uncommitted: $dirty files"
```

### 3. Detect Workflow Phase
Based on current state, suggest the right skill:

| Signal | Phase | Skill |
|--------|-------|-------|
| No CLAUDE.md or tasks/ | **Kickoff** | `/project init` or `project-kickoff` |
| No spec file, new feature | **Spec** | `spec-interviewer` |
| Spec exists, no code | **Plan** | `writing-plans` or `/plan-eng-review` |
| Active todo items | **Build** | Continue working |
| Code written, no tests | **Verify** | `verification-before-completion` |
| Tests pass, ready to ship | **Ship** | `/ship` or `/pr` |
| Just shipped | **Retro** | `/retro` |

### 4. Report
```
πŸš€ Session Ready
  Project: {name}
  Branch: {branch}
  Phase: {detected phase}
  Suggested: {skill name}
  Tasks: {X incomplete / Y total}
```

## Gotchas
- Don't spend more than 10 seconds on startup β€” it should be fast
- If no project context, just greet and ask what we're working on
- Never auto-run destructive commands during startup
- MCP servers connect automatically β€” don't test them unless asked

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.