메뉴
Use when starting a new coding session, beginning work on a branch, or resuming after a context reset. Gathers branch context, in-progress work, plan documents, and recent history to produce a briefing before any code is written.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | start-session |
| description | Use when starting a new coding session, beginning work on a branch, or resuming after a context reset. Gathers branch context, in-progress work, plan documents, and recent history to produce a briefing before any code is written. |
Orientation before action. Gather context from the current branch, git state, plan documents, and recent history, then present a structured briefing.
Announce at start: "Using start-session to orient before we begin."
# Branch name
git branch --show-current
# Is this main or a feature branch?
# main/master = fresh start, anything else = in-progress work
# Uncommitted changes
git status --short
# Recent commits on this branch (diverged from main)
git log main..HEAD --oneline 2>/dev/null || git log --oneline -5
Based on the branch name, find relevant context:
# Search for plan docs matching branch topic
ls docs/plans/ | grep -i "<branch-topic-keywords>"
# Also check for today's date or recent dates
ls docs/plans/ | tail -10
If a plan doc exists, read it and extract:
# Search GitHub issues related to branch topic
gh issue list --search "<branch-topic-keywords>" --state all --limit 5
# What was the last session working on?
git log --oneline -10 --format="%h %s (%ar)"
# Any stashed work?
git stash list
Search the MCP memory service for context relevant to the branch topic or planned work:
memory_search(query: "<branch-topic-keywords>", limit: 5)
memory_search(query: "gotchas <area>", limit: 5)
Look for:
Include relevant brain findings in the briefing under a "Brain Context" section.
Quick health check — catch problems before they compound:
# Are there uncommitted changes that might be from a crashed session?
git status --short
# Are we behind main?
git fetch origin main --quiet 2>/dev/null
git rev-list HEAD..origin/main --count 2>/dev/null
Format the gathered information as a structured briefing:
## Session Briefing
**Branch**: `<branch-name>` (diverged from main by N commits)
**Status**: <fresh | in-progress | uncommitted changes detected>
### Context
- <Plan doc summary if found, or "No plan doc found">
- <Related issues if found>
- <Recent commit summary>
### Relevant Skills
Based on the branch topic, these skills are likely relevant:
- <skill-1>: <why>
- <skill-2>: <why>
### Suggested Next Steps
- <Based on branch state and plan doc status>
After presenting the briefing, ask:
Does this look right? What are we working on today?
Wait for human confirmation before proceeding to any code changes. The briefing may be wrong or outdated — the human corrects course here.
Branch names encode intent:
| Prefix | Meaning | Expected workflow |
|---|---|---|
feat/ | New feature | Plan → implement → test → PR |
fix/ | Bug fix | Investigate → fix → regression test → PR |
refactor/ | Code improvement | Understand scope → refactor → verify tests → PR |
docs/ | Documentation | Draft → review → PR |
chore/ | Maintenance | Execute → verify → PR |
Map branch topics to relevant skills:
| Topic keywords | Skills to suggest |
|---|---|
| video, proxy, stream, hls | express5-api-patterns, stash |
| sync, instance, multi | express5-api-patterns, prisma-sqlite-expert |
| ui, component, page, layout | visual-style, react-spa-performance |
| test, coverage, spec | writing-tests, vitest |
| release, version, deploy | release-workflow |
| restriction, exclusion, permission | prisma-sqlite-expert, express5-api-patterns |
| migration, schema, database | prisma-sqlite-expert |
| playlist, rating, stats | express5-api-patterns, prisma-sqlite-expert |
| graphql, codegen, stash-client | graphql-patterns, stash |
work-ticket (which handles the full ticket lifecycle)Use when writing tests for peek-stash-browser. Covers Vitest + React Testing Library (client) and Vitest + integration testing (server). Follow these conventions exactly.
Run all validation checks before tagging a new release
Perform a code quality review before creating a PR. Use when reviewing changes, checking code quality, or doing a self-review of the current branch. Invoked as part of the work-ticket lifecycle after verification-before-completion and before finishing-a-development-branch.
Use when preparing or executing a release of peek-stash-browser. Covers the full release lifecycle from validation through Docker image publishing.
Express 5 patterns for peek-stash-browser — TypeScript backend serving a React SPA with HLS video proxying, multi-instance Stash server routing, JWT auth via HTTP-only cookies, and SQLite via Prisma. Use when writing or modifying Express route handlers, middleware, proxy controllers, or streaming endpoints in the peek project.
Expert guidance for Prisma ORM with SQLite databases. Use when designing schemas, writing migrations, optimizing queries, working with FTS5 full-text search, or troubleshooting SQLite-specific issues in Node.js/TypeScript applications.