vulcanshen

Clerk — Documentation skill for Claude Code

Documentation community

Auto-summarize Claude Code sessions as local markdown — session summaries, keyword index, on-demand reports.

How to install Clerk

This entry records only its repository, not the path inside it, so there is no exact command to give. Open vulcanshen/clerk and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Clerk does

Auto-summarize Claude Code sessions as local markdown — session summaries, keyword index, on-demand reports.

Alternatives in Documentation

会话管理（Session Manager）需求文档（PRD / Markdown） — 目标：对 Codex / Claude Code 的本地会话记录进行可视化管理，并提供“一键复制 / 一键终端恢复”能力 31.7k ★
Napkin — You maintain a per-repo markdown runbook, not a chronological log 420 ★
Wiki Init — Scaffold an empty llmwiki — create raw/, wiki/, site/ directories and seed wiki/index.md, wiki/log.md, wiki/ov 375 ★

README

 ______     __         ______     ______     __  __    
/\  ___\   /\ \       /\  ___\   /\  == \   /\ \/ /    
\ \ \____  \ \ \____  \ \  __\   \ \  __<   \ \  _"-.  
 \ \_____\  \ \_____\  \ \_____\  \ \_\ \_\  \ \_\ \_\ 
  \/_____/   \/_____/   \/_____/   \/_/ /_/   \/_/\/_/

[![GitHub Release](https://img.shields.io/github/v/release/vulcanshen/clerk)](https://github.com/vulcanshen/clerk/releases) [![Go Version](https://img.shields.io/github/go-mod/go-version/vulcanshen/clerk)](https://go.dev/) [![Go Report Card](https://goreportcard.com/badge/github.com/vulcanshen/clerk)](https://goreportcard.com/report/github.com/vulcanshen/clerk) [![License](https://img.shields.io/github/license/vulcanshen/clerk)](LICENSE)

[繁體中文](README.zh-TW.md) | [日本語](README.ja.md) | [한국어](README.ko.md)

**Most AI tools are built for AI. clerk is built for humans.**

Your Claude Code sessions disappear when you close the terminal. clerk turns them into a searchable knowledge base that you own.

The Problem

It's Friday afternoon. Time for the weekly report. You open `git log` and try to reconstruct what you actually did across three projects, eight sessions, and five days. Half the work isn't even in git — it was debugging, research, architecture decisions, conversations with Claude about trade-offs you've already forgotten.

Claude Code doesn't remember across sessions. And you shouldn't have to.

Why not just ask Claude?

You could try. Open Claude Code and ask "what did I do last week?"

It doesn't know. It only sees the current session. To look back, you'd need to find the right session ID, load it with `--resume`, ask for a summary, then repeat for every session across every project. Each time, Claude re-reads the entire raw transcript — burning tokens to reconstruct what could have been saved in a single markdown file.

clerk takes a different approach: one API call per session, at the moment it ends, producing an incremental summary stored as plain markdown. By Frida