# claude-sessions — Session Tracking Slash Commands

> Add /project:session-* commands to Claude Code to track goals, progress notes, and end-of-session summaries across days of development.

## Install

Save the content below to `.claude/skills/` or append to your `CLAUDE.md`:

## Quick Use

```bash
git clone https://github.com/iannuttall/claude-sessions.git
mkdir -p .claude/commands
cp -r claude-sessions/commands/* .claude/commands/
mkdir -p sessions && touch sessions/.current-session
# In Claude Code: /project:session-start <name>
```

## Intro

Add /project:session-* commands to Claude Code to track goals, progress notes, and end-of-session summaries across days of development.

**Best for:** Developers who want continuity: clear goals, progress logs, and handoff-ready summaries

**Works with:** Claude Code custom slash commands stored in project `.claude/commands/` (or `~/.claude/commands/`)

**Setup time:** 5-12 minutes

### Key facts (verified)

- GitHub: 1202 stars · 140 forks · pushed 2025-06-16.
- License: MIT · owner avatar + repo URL verified via GitHub API.
- README-backed entrypoint: `/project:session-start`.

## Main

- Use session-start/update/end as a lightweight project journal: the goal is continuity, not perfect documentation.

- Keep sessions out of Git if you prefer: README suggests adding `sessions/` to `.gitignore` when the log is personal or sensitive.

- Customize safely: start by adjusting paths/prefixes, then add team-specific commands once the core loop works.

### Source-backed notes

- README documents six commands: session-start, session-update, session-end, session-current, session-list, session-help.
- README states commands use the `/project:` prefix and store session state via a `.current-session` file.
- README includes a note on adapting to Claude Code's standard `.claude/commands/` directory structure.

### FAQ

- **Where are sessions stored?**: README uses a `sessions/` directory plus a `sessions/.current-session` pointer file by default.
- **Can I share sessions with my team?**: Yes, but consider privacy. README suggests adding `sessions/` to `.gitignore` if you don't want it tracked.
- **Do these commands work outside Claude Code?**: They are written for Claude Code's custom slash command system; other tools may need different wiring.

## Source & Thanks

> Source: https://github.com/iannuttall/claude-sessions
> License: MIT
> GitHub stars: 1202 · forks: 140

---

<!-- ZH -->

## Quick Use

```bash
git clone https://github.com/iannuttall/claude-sessions.git
mkdir -p .claude/commands
cp -r claude-sessions/commands/* .claude/commands/
mkdir -p sessions && touch sessions/.current-session
# In Claude Code: /project:session-start <name>
```

## Intro

为 Claude Code 添加一组 /project:session-* 命令（start/update/end/current/list/help），把目标、进度与总结写入 sessions/ 文件夹，方便跨多天持续开发与交接。

**Best for:** 需要“持续对齐上下文”的开发者：目标、进度日志与可交接的会话总结

**Works with:** Claude Code 的自定义斜杠命令（项目 `.claude/commands/` 或 `~/.claude/commands/`）

**Setup time:** 5-12 minutes

### Key facts (verified)

- GitHub：1202 stars · 140 forks；最近更新 2025-06-16。
- 许可证：MIT；作者头像与仓库链接均已通过 GitHub API 复核。
- README 中可对照的入口：`/project:session-start`。

## Main

- 把 session-start/update/end 当作轻量工程日志：核心是“连续性”，不是写完美文档。

- 如果会话日志偏个人或含敏感信息，可以按 README 建议把 `sessions/` 加进 `.gitignore`。

- 逐步定制：先对齐目录与前缀，再扩展团队自己的命令，避免一上来就复杂化。

### Source-backed notes

- README 列出 6 个命令：session-start/session-update/session-end/session-current/session-list/session-help。
- README 说明命令使用 `/project:` 前缀，并通过 `.current-session` 文件追踪当前会话。
- README 给出适配标准 `.claude/commands/` 目录结构的说明。

### FAQ

- **会话文件存在哪里？**：README 默认示例使用项目根目录的 `sessions/`，并用 `sessions/.current-session` 指向当前会话。
- **能和团队共享会话日志吗？**：可以，但要考虑隐私。若不想纳入版本控制，按 README 建议把 `sessions/` 加入 `.gitignore`。
- **能在 Claude Code 之外使用吗？**：内容为 Claude Code 自定义斜杠命令编写；其他工具需要不同的接入方式。

## Source & Thanks

> Source: https://github.com/iannuttall/claude-sessions
> License: MIT
> GitHub stars: 1202 · forks: 140


---
Source: https://tokrepo.com/en/workflows/claude-sessions-session-tracking-slash-commands
Author: Skill Factory