session-start

To analyze repository state before a coding session, the skill autonomously runs parallel git queries, VCS checks, and SSOT freshness validation to surface risks. It enforces bootstrap gates to ensure project readiness and safely resume unfinished work.

Initializing and aligning a repository for feature development requires aggregating historical metrics, recognizing recurring patterns, and checking environment configurations. This provides structured recommendations and uses AskUserQuestion flows to align session focus before handing off to planning.

Checking SSOT freshness and environment readiness in a git repository involves performing baseline quality probes and cross-repo inspections during session initialization. This validates that source of truth files are current and the local environment meets bootstrap gating criteria.

Session-start requires access to local repository files to analyze VCS status, while platform CLIs are optional. It performs git queries and cross-repo inspections autonomously, meaning it can function with just local repository access but integrates platform data when CLIs are present.

Resuming an unfinished engineering session safely is handled by enforcing a hard bootstrap gate and respecting persistence state. The system identifies ongoing work, prevents unsafe continuations, and surfaces previous session context to ensure aligned and structured resumption.

Structured repository analysis for engineering sessions is needed when starting housekeeping, feature development, or deep coding work. It ensures teams begin with clear recommendations, cross-repo status awareness, and safety gates rather than manually inspecting project readiness.