I've been helping teams learn how to leverage Claude Code the best and I've built a couple of complimentary tools to help people learn from each other.

This replay TUI, claude-replay, which lets you explore and revisit your past Claude Code sessions. And a companion optional Claude Code plugin, claude-session-trail, to automatically store your sessions in a dedicated git branch: https://github.com/Trailblaze-work/claude-session-trail

Both tools can work in tandem, as the replay client can also read project sessions from the git branch, in addition to its default of accessing the user's local sessions.

This is hot off the press, so there might be some rough edges still, but the base functionality you would expect works. I think they have purpose as learning tools at a minimum, and can be useful for self-introspection.

The automatic committing is probably too much for mature teams, for whom the export/sharing functionalities of specific sessions might be enough.

Yes, models change and what works in terms of prompting strategy now might not work on newer models in the future, but at the moment everyone develops strategies and good habits locally in parallel. Being able to look over someone's shoulders and seeing how they do it might be useful. And it lowers the effort required to share how you work inside Claude Code with others if you wish to do so.

Contributions welcome!