session-start
Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context.
AlexZio00 · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlexZio00/sovereign-skills --skill session-start技能说明
skill_type: lifecycle tools: Read, Write triggers:
- "/session-start"
- "세션 시작"
- "이어서 해줘"
- "어디부터"
- "start session"
name: session-start
description: "Load handoff on session start, review lessons, output readiness signal. Triggers: '/session-start', 'start session'. Skip if: first session (no handoff), user requests 'start fresh', or standalone question unrelated to project context."
user_invocable: true
depends_on:
skills: []
agents: []
files:
- memory/session-handoff-LATEST.md
- tasks/lessons.md
- memory/MEMORY.md
- memory/context-log.md
- ~/.claude/STATE.md
- ~/.claude/settings.json
- ~/.claude/settings.local.json
- ~/.claude/.harness/interventions/
- ~/.claude/memory/model-diff-ledger.md concurrency_profile: read_only: true concurrency_safe: true destructive: none
(removed 2026-06-10) context: !cat — non-standard YAML tag, breaks parser. Handoff injection is handled by SessionStart hook
not_for:
- "First session (no handoff exists) -> start directly"
- "One-off question -> answer directly"
- "User says 'start fresh' -> skip" see_also:
- skill: session-checkpoint relation: "lifecycle pair — open/close"
Session Start
Dominant Variable
Does the handoff document what to do next, or what was done? If it lists completed work, the handoff was written incorrectly. If Priority 1 cannot be identified immediately, deepen your inspection of Phase 1.
Trigger
/session-start- "start session"
- "continue from where"
- "where did we get"
- (Korean language triggers handled in YAML frontmatter above)
Discard If
memory/session-handoff-LATEST.mdmissing (first session) → skip, start fresh- User requests "start fresh" / "ignore context" → skip
- Project-unrelated standalone question → skip
Phase 0.5 runs even on discard: configuration errors must be detected in first session and standalone questions too.
Key Assumptions
- memory/session-handoff-LATEST.md exists — if broken: fallback to "new session" mode. Do not synthesize handoff.
- tasks/lessons.md exists — if broken: skip lesson review Phase.
- settings.json parseable — if broken: skip health-check Phase only; proceed normally with rest.
Phase 0.5: Environment Health Check
Warnings only — no blocking. Use Read tool only (no modifications).
Check 1 — Model ID (read ~/.claude/settings.json):
- Confirm
"model"field value → warn if outside this list:["opus", "sonnet", "haiku", "fable", "claude-sonnet-5", "claude-opus-4-8", "claude-opus-4-7", "claude-sonnet-4-6", "claude-haiku-4-5", "claude-opus-4-5", "claude-sonnet-4-5", "claude-fable-5"] # Context suffixes like [1m]/[200k] are stripped before comparison (e.g., claude-fable-5[1m] → claude-fable-5) - Message:
⚠️ settings.json model ID invalid: "{value}" — please update - If file missing: skip silently
Check 2 — Accumulated Allow Entries (read ~/.claude/settings.local.json):
- Count
permissions.allowarray items - If count > 5 →
⚠️ settings.local.json allow: N entries - If file missing: skip silently
Note — session-scoped authorization does not carry over: one-time approvals for risky actions, temporarily-enabled high-risk feature flags, and other session-scoped permissions granted in a previous session are not restored automatically in a new session. If the handoff notes something as "approved" or "enabled," treat that as historical context only — ask the user to re-confirm before relying on it this session.
Output rule: Both clean → no output (omit environment-alerts line in Phase 5). If warnings present, display in Phase 5 **Environment alerts:** line.
Phase 1: Load Handoff
Read memory/session-handoff-LATEST.md (auto-injected above).
Extract:
- Priority 1 — most urgent task for this session
- Outstanding decisions — questions awaiting user input
- Remaining issues — unresolved bugs or blockers
- Context notes — failed approaches from previous session (prevent repetition), critical causal links
If file empty or missing: output [No handoff — starting fresh] and stop.
Phase 2: Review Lessons
Read tasks/lessons.md.
2.0 Load Graduated Gates (always-on — highest priority)
Extract the ## Graduated Gates (Graduated Gates) table section. Output it regardless of conf filter — these are verified gates (conf≥0.7 AND obs≥3), so always-on exposure is intentional (Loop B self-correction enforcement layer). In Phase 5 **Graduated gates:** line, compress each gate as trigger → check on one line.
Nature (user-specified, 2026-06-04): Gates are "expose → consult → decide" tools. Pause before the triggering action, check, and consult if unclear. Not automatic execution; not auto-generated. Their role is to surface decisions left to the user and conversation.
Skip section if missing.
2.1 Scan Related Lessons
Scan correction rules relevant to today's planned work:
- Code changes expected → check that domain's correction rules
- Commit/push planned → check commit-related rules
- Debugging planned → check debugging anti-patterns
v2 metadata line usage (> conf · seen · obs, from 2026-04-28~):
conf ≥ 0.7(verified/core) → one-line summary from body (priority exposure/signal)conf 0.5(normal/Opus-triggered) → title only on one lineconf < 0.5(experimental/unresolved) → header title only or skip (noise control)seenwithin 30 days +obs ≥ 3= active pattern — priority exposure- v2 metadata absent = legacy lesson, treat normally (backward compat)
Flag one line per matching rule. Skip silently if file missing.
2.2 Model Difference Analysis Reminder (semi-automatic — deterministic check)
Trigger for converting accumulated model-tagged behavior observations into rules. Periodic reminder to digest model tag backlog into patterns → rules.
Deterministic commands (run in order — each is a single
阅读完整来源 ↗