* main.go: resolvePlans implementing the R5.1 / design §3.5 decision
tree — Case A (explicit path stat) and a unified upward walk for
Cases B (cwd inside plan dir) and C (cwd ancestor has dev/plans/)
with archive/ filter and lex sort; Case D returns the 3-option
error. No downward WalkDir.
* Hand-rolled parseLintFlags accepting --format={text,json},
--strict, --no-ears, --color={auto,always,never} (no-op per D-1),
both --flag=value and --flag value forms. Unknown flag → error.
* runLint orchestrator: resolvePlans → loadPlan (reads prd/design/
tasks via Scan + os.Stat for close-out markers) → lintPlan
(BuildIndex + 4 rule checkers, missing-PRD short-circuit per R3.2,
PlanDir backfill, sortDiagnostics). Placeholder text emitter —
task 6 replaces with the full emitText/emitJSON from design §3.7.
* computeExit returns 0/1 per R5.4/R5.5; 2 is reserved for outer
discovery/I-O failures (runLint returns 2 directly on those paths).
* main_test.go: TestResolvePlans covers Cases A (valid + invalid), B
(deeply-nested cwd), C (3 plans + archive filter + lex sort), D
(no ancestor); TestParseLintFlags covers every documented flag
plus unknown-flag rejection and last-value-wins. The prior stub
test TestRun_LintStub was replaced with TestRun_LintMissingPRD —
the stub assertion no longer holds now that runLint actually runs
the pipeline. Output-format assertions may need revision when
task 6.6 lands per tasks.md 5.6 note.
Parent task 5.0 from dev/plans/26172-planctl/tasks.md.
Codex code-review session: 019db2ca-721d-7b11-8760-639b2588b114 (1 round, approved on R1).
|
||
|---|---|---|
| .claude | ||
| cmd | ||
| dev | ||
| scripts | ||
| .gitignore | ||
| AGENTS.md | ||
| CLAUDE.md | ||
| go.mod | ||
| go.sum | ||
| INTEGRATION.md | ||
| README.md | ||
jj-template
Reusable jj + Claude Code workflow template. Provides automatic per-session snapshot management so every Claude Code session's work is committed and isolated — even with concurrent agents.
What It Does
- Session start: snapshots any pre-existing uncommitted work before the agent starts editing
- Post-edit: tracks every file Claude edits (via Edit/Write/NotebookEdit tools) per-session
- Session end: commits tracked files with a descriptive
wip(claude:<session>):message, then commits any untracked leftovers - Concurrent safety: multiple agent sessions on the same repo get isolated, file-scoped commits
- Bookmarks: each session's commit gets a
wip/claude-{session}bookmark for easy reference - Base tracking: records the starting revision per session (visible in
status) - Orphan reaping: dead sessions (crashed CLI) are cleaned up automatically via PID liveness checks and 30m timeout (configurable via
JJ_HOOK_STALE_MIN) - Legacy cleanup: daemon sweeps orphaned
/tmp/jj-claude-*-filesfrom pre-daemon hook versions on startup - Conflict detection: warns when multiple sessions edit the same file
- Squash:
squash-wipconsolidates accumulated wip commits into one for cleaner history - Auto-squash: set
JJ_HOOK_AUTO_SQUASH=1to squash automatically at session end - Repo cleanup:
/repo-cleanupClaude command organizes wip commits into themed conventional commits
Commit Daemon (jj-commitd)
A Go daemon that batches file edits into debounced commits via a Unix socket.
- How it works:
session-startlaunches the daemon;post-editsends file paths over a socket; a debounce timer (default 3s) batches edits into a singlejj commit;session-endflushes pending commits and shuts down - Build:
go build -o bin/jj-commitd ./cmd/jj-commitd/orgo install ./cmd/jj-commitd/ - Config:
JJ_HOOK_DEBOUNCE_SEC(default3),JJ_HOOK_STALE_MIN(default30) - Session inventory: on
session-start, returns list of other active sessions and their files - Logging: daemon log at
/tmp/jj-commitd-{repo_id}.log - Fallback: if the binary is not found, the hook falls back to file-tracking-only mode (commits at session end)
Prerequisites
- jj (Jujutsu VCS)
- jq (JSON processor)
- Claude Code CLI
- Go 1.22+ (optional, for building the commit daemon)
Quick Start
See INTEGRATION.md for step-by-step instructions to add this to an existing or new project.
Files
cmd/jj-commitd/
main.go # Commit daemon (Go)
scripts/
_lib.sh # Shared utilities (REPO_ROOT resolution)
jj-hook.sh # Main hook script (all 6 actions)
test-jj-hooks.sh # 26-test integration suite
.claude/
settings.json # Hook configuration for Claude Code (team-shared)
commands/
repo-cleanup.md # /repo-cleanup slash command
Manual Commands
# Check active sessions for this repo
./scripts/jj-hook.sh status
# Squash all wip commits between main and @ into one
./scripts/jj-hook.sh squash-wip
# Force-reap all non-alive sessions
./scripts/jj-hook.sh reap
How It Works
Tracking Files
Each active session gets a tracking file at /tmp/jj-claude-{REPO_ID}-{SESSION_ID}-files. The REPO_ID is a cksum of the repo root path, preventing cross-repo contamination. Companion files record the parent process (-pid) and starting revision (-base) for liveness checking and cleanup context.
Commit Flow
With daemon (default when jj-commitd binary is available):
session-start → snapshot pre-existing work
→ launch jj-commitd daemon (or connect to existing)
→ record base revision, reap stale sessions
post-edit (per file) → send file path to daemon via Unix socket
→ daemon resets debounce timer (3s default)
→ on timer expiry: commit all batched files
session-end → flush pending commits (daemon commits immediately)
→ set wip/claude-{session} bookmark
→ commit untracked leftovers (if sole session)
→ auto-squash (if JJ_HOOK_AUTO_SQUASH=1)
→ clean up tracking + PID + base files
Without daemon (fallback):
session-start → snapshot pre-existing work
→ record base revision, initialize tracking file
→ reap stale/orphaned sessions
post-edit (per file) → append relative path to tracking file (dedup)
session-end → commit tracked files (file-scoped)
→ set wip/claude-{session} bookmark
→ commit untracked leftovers (if sole session)
→ auto-squash (if JJ_HOOK_AUTO_SQUASH=1)
→ clean up tracking + PID + base files
Concurrency
When multiple Claude sessions edit the same repo simultaneously:
- Each session tracks its own files independently
- Session A ending only commits files A touched
- Untracked changes (Bash-created files) are only committed when the last session ends
- If both sessions touch the same file, the first to end commits it; the second skips it (no diff remaining)
Tests
scripts/test-jj-hooks.sh
Runs 34 integration tests in temporary jj repos. Requires jj and jq. Portable across macOS and Linux.