ALWAYS invoke this skill FIRST at session start, after context reset/compaction, or when user mentions "reset", "new session", "where were we", "what was I working on". Do NOT skip this for specific task requests—orient first, then execute. This is Rule 0.
The `sdv-session-start` skill is designed to provide a structured and efficient ramp-up at the beginning of a development session. It addresses the common challenge developers face when resuming work after a break, switching branches, or recovering from a context reset. By systematically gathering information from project journals, git status, and build state, this skill ensures that developers are immediately aware of the current project context, pending tasks, and any potential blockers before starting new work. It prevents wasted time and reduces the risk of errors caused by forgetting the previous session's progress or the current branch's state.
Key features of this skill include identifying the current git branch, reading the associated branch journal to summarize previous work, checking git status and recent commits, verifying build success, and reviewing pending tasks and known issues. It provides a clear orientation checklist and a report template to document the current session's state. Additionally, it offers quick commands for automation, context recovery procedures for compacted or reset sessions, and conventions for journal and branch naming, ensuring consistency and easy traceability across sessions.
This skill is particularly useful for software developers, teams using version control with git, and individuals working on long-running or complex projects that require frequent context switching. It is ideal for anyone who wants to streamline session startup, maintain continuity in development, and minimize the cognitive load of recalling previous work. Use cases include starting new development sessions, resuming after breaks, switching branches, recovering from context resets, or anytime clarity about the current project state is required.
You should use this skill at the start of a new development session, after context compaction or reset, when resuming work after a break, switching branches, or whenever you are unsure about the current state of your work.
This skill relies on git for branch and commit information, project journal files located in `Docs/journals/`, build tools such as `dotnet build`, and documentation files like `Docs/ROADMAP.md` and `Docs/BUGS.md`.
No, the skill does not automatically resolve build errors or complete pending tasks. It provides orientation, context summaries, and checklists so you can address issues manually.
Yes. Journals follow the format `YYYY-MM-DD_branch-name.md` and are stored in `Docs/journals/`. Branches typically follow `liminalwarmth/feature-name` for features, `liminalwarmth/fix-name` for bug fixes, and `master` for the main branch.
You should read the `CLAUDE.md` handbook first, check the branch journal, review `git diff`, run a build to verify the current state, and ask the user for clarification if any context is unclear.
Quick Setup:
.claude/skills/Repository
liminalwarmth/StardewOutfitManager