메뉴
Use when starting a dev session on Buddy Evolver, or to refresh project context. Use when the user says "start session", "refresh context", "what tools do I have", or "session status".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | session-start |
| description | Use when starting a dev session on Buddy Evolver, or to refresh project context. Use when the user says "start session", "refresh context", "what tools do I have", or "session status". |
Manual re-trigger of the SessionStart hook. Use this when the original hook output has scrolled out of context, or when you want a fresh snapshot of project state (binary status, git state, skills, agents, hooks, compatibility).
The SessionStart hook at hooks/session-start.sh is the single source of truth for session context. This skill delegates to it so there is no hardcoded list to drift.
CLAUDE_PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT}" bash "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"
Present the output verbatim to the user inside a code block.
Scan the hook output for these markers and, if present, surface them above the verbatim output as a short "Action needed" header:
⚠ STALE in the Main line → recommend: git pull --rebase origin main or rebase the branchbackup_status: no backup → recommend: evolve first before reset operationsPending cleanup: line with non-zero failed count → note that retry happens on next sessionIf everything is healthy, end with:
"You are in Phase 1 (Plan). Describe what you want to build, and I will design the implementation plan before writing any code. Run /session-execute when the plan is approved."
If warnings were surfaced, ask whether the user wants to address them now or defer.
hooks/session-start.sh.This skill should be used when the user asks to "security audit", "check security", "audit buddy", "check backup health", "verify backup", or "security check".
This skill should be used when the user asks to "clean cache", "cache clean", "clear build cache", "free disk space", "clean up", "remove build artifacts", "clean .build", "manage cache", or "show cache size".
This skill should be used when the user asks to "token review", "review tokens", "optimize tokens", "audit context size", "reduce token footprint", "session review", "end of session review", or "check token usage".
Pre-commit pipeline for Buddy Evolver — runs token optimization, full test-all.sh, security review, docs sync, and comment audit. INVOKE IMMEDIATELY when the user says any variant of "session review", "review session", "session end", "end session", "end the session", "ending session", "session over", "session done", "wrap up", "wrapping up", "finish up", "finishing up", "done for now", "close out", "ready to commit", or "before commit" — treat these as direct invocations, not topics for discussion. Do NOT ask whether the timing is right, do NOT argue that a commit already happened (run anyway and report what's still actionable), do NOT defer. If the user actively says "don't run" or "skip", honor that — otherwise invoke now.
This skill should be used when the user asks to "sync docs", "update docs", "sync documentation", "update readme", "update claude md", "docs out of date", "check documentation", or "fix docs".
Use after a PR is merged to GitHub main. Syncs local main, verifies the merged code builds, removes merged worktrees, and stages the current worktree for automatic self-cleanup on /exit. With --release, also bumps version, updates CHANGELOG, tags the commit, pushes to trigger marketplace publish, and verifies the local plugin reloads. Use when the user says "deploy", "session deploy", "pr merged", "post-merge sync", "deploy session", "clean up after merge", or "release new version".