一键导入
round
Use when transitioning between work sessions and wanting to pick up where the previous session left off.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when transitioning between work sessions and wanting to pick up where the previous session left off.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when deciding how to manage, audit, sync, enable, disable, or troubleshoot skills and agents with the skillshare CLI across Claude Code, Codex, Gemini, OpenCode, Kiro, Goose, Pi, Antigravity, or project-local .skillshare setups. Especially use for questions about global vs project mode, disabled-by-default policies, .skillignore/.agentignore, target drift, broken symlinks, duplicate skills, sync dry-runs, or whether to use skillshare versus a runtime-native tool such as Codex skill-manager.
Use when creating git commits or reviewing commit messages. Ensures messages follow the Conventional Commits specification v1.0.0, which enables automated changelogs and semantic versioning. Invoked when the user wants to commit changes, craft a commit message, or validate an existing one.
Use when user references previous work phases, tasks, or discussions from prior sessions not present in current conversation context.
Use when designing or reviewing Python classes, deciding where logic belongs, or recognizing antipatterns like helper classes, utility bags, and god objects.
Use when crafting prompts that require factual accuracy, working with long documents, generating claims that need verification, or when outputs must be auditable and grounded in source material
Use when: tracking work, adding todos, filing bugs, managing tasks/issues, checking what to work on, planning epics, deferring work, pre-PR checks, or any mention of bd/beads. Covers the full bd CLI.
| name | round |
| description | Use when transitioning between work sessions and wanting to pick up where the previous session left off. |
Search for the most recent session note in the project's .claude-sessions/ directory:
ls -t .claude-sessions/*.md 2>/dev/null | head -1
If no session notes exist, proceed to Step 4 (create new session).
Read the latest session note and extract:
Display a concise summary:
📁 Previous session: <filename>
Status: <status>
Next: <next steps>
Blockers: <blockers or "None">
Rename the previous note with timestamp to preserve it:
# Get current timestamp
TIMESTAMP=$(date +%H%M%S)
# Rename: 2025-02-19-upload-debug.md → 2025-02-19-upload-debug-142035.md
mv .claude-sessions/<old-file> .claude-sessions/<base>-<timestamp>.md
If file already has timestamp, keep as-is.
Generate new session note from template:
.claude-sessions/YYYY-MM-DD-<topic>.mdTemplate structure:
# Session: <Topic> - <Date>
## Branch
`<current-git-branch>`
## Context
[Loaded from previous session summary]
## Goals This Session
- [ ] <from previous "Next Steps">
- [ ] <additional goals>
## Progress Log
*To be updated during session*
## Blockers / Questions
[Carry over from previous session]
## Notes
*
Create .claude-sessions/ directory if it doesn't exist.
Gather and display:
Git status:
git branch --show-current
git status --short
git log --oneline -3
Key project files (if they exist):
CLAUDE.md or .claude/CLAUDE.md - Project instructionsAGENTS.md - Agent guideTODO.md or ROADMAP.mdDisplay summary:
---
🔄 New session: <filename>
Git: <branch> (<X> uncommitted changes)
Recent commits:
- <commit 1>
- <commit 2>
- <commit 3>
Ready to continue.
Acknowledge the transition is complete and wait for user direction.
<template_usage>
Use the session note template from templates/session-note.md:
.claude-sessions/YYYY-MM-DD-<topic>.md
</template_usage><error_handling>
<success_criteria>