Committer
Update the project diary before a commit — review staged files, determine LIGHTWEIGHT vs FULL session-historian mode based on what's staged, write the diary entry, and stage the diary changes. Does not create the commit; a plugin hook enforces that diary files are staged before `git commit` runs.From its SKILL.md
npx -y skills add humantypo/memtoad --skill committerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.8 KB, as published. Nobody here has run it
Run the following steps inline in the main conversation. Never spawn an agent.
Step 1 — Check working state
Run both commands:
git diff --cached --name-only
git status --short
If there are no staged files AND no modified/untracked files: stop. Tell the user there is nothing to commit.
Display the current state to the user: which files are staged, which are modified-but-not-staged.
Step 2 — Assess session-historian mode
From Step 1's output, determine the mode.
Skip session-historian entirely if every staged path is documentation-only:
diary/CLAUDE.md.claude/(skills, commands, agents)- Any
.mdfile at the repo root
In that case, tell the user the staged changes are documentation-only and no diary update is needed, then stop.
Otherwise determine the historian state file path dynamically:
STATE_FILE=~/.claude/projects/$(pwd | tr '/' '-' | sed 's/^-//')/historian_state.json
cat "$STATE_FILE" 2>/dev/null || echo '{"last_full_run_date":"1970-01-01","commits_since_last_full":0}'
Choose FULL mode if ANY of the following are true:
- Any staged file has a code extension:
.py,.ts,.tsx,.js,.jsx,.go,.rb,.java,.rs,.cs,.cpp,.c,.swift,.kt,.sh,.bash - Any staged file has
A(added) orD(deleted) status commits_since_last_full≥ 5last_full_run_dateis more than 3 days before today
Otherwise: LIGHTWEIGHT mode.
Step 3 — Run session-historian and stage diary changes
Run session-historian inline using the rules in the session-historian skill:
LIGHTWEIGHT: Update only diary/session_context.md. Append to diary/lessons_learned.md only if something non-obvious was learned this session. Do not touch diary/architectural_decisions.md.
FULL: Update diary/session_context.md. Append to diary/architectural_decisions.md only if a new architectural decision was made. Append to diary/lessons_learned.md only if a new lesson was learned.
Do not reference the commit hash in diary entries — it isn't known yet, and this skill does not create the commit.
After writing, stage the diary changes:
git add diary/
Report to the user that the diary is updated and staged. Do not commit — a plugin PreToolUse hook checks that diary/ is staged before any git commit runs, and denies the commit with a pointer back to /memtoad:committer if it isn't. Once diary changes are staged, the user's normal commit flow (or the harness's own commit drafting) can proceed.