coja
1e39e0cb4b
Supersedes the old flat .config/ layout (last published 2026-06-28) with the private repo's structure: one shared base plus per-host overlays. - packages: common/ gui/ lw/ fl/ wm/ plus install.sh and bin/ tooling (dotsync, reconcile-hyde.sh) - new README covering the layout, deploy order and the HyDE dependency - current HyDE waybar rig (layouts/, cava), pi agent extensions, claude/ config, tmux, presenterm, aichat roles - fish: kp (keepassxc-cli + fzf picker, db path from $KP_DB) and bind_M_n_history (alt+1..9 recalls the nth history entry) - drops cruft that should never have been tracked: the duplicate top-level .pi/ copy, btop.log, zellij config.kdl.bak, fish_variables - .pi/agent/auth.json is gitignored; auth.json.example ships instead Host-specific work sessions and the personal backlog stay in the private tree. Endpoint locators in the llamacpp/whisper guides are placeholders ($SERVER, <own-domain>) — the guides themselves stay, since they are the useful part.
3.1 KiB
3.1 KiB
description, argument-hint, disable-model-invocation, allowed-tools
| description | argument-hint | disable-model-invocation | allowed-tools | |
|---|---|---|---|---|
| Draft a commit message for the staged changes, matching this repo's commit style, then print it in the reply, save it to the repo's CLAUDE_COMMIT_MSG file, and copy it to the clipboard. Never stages or commits. Use once you've staged what you want to commit. |
|
true | Bash(git diff:*), Bash(git log:*), Bash(git status:*), Bash(git rev-parse:*), Bash(wl-copy:*), Read, Glob, Write |
Draft a commit message for the staged changes
Context for the current commit — what's staged, plus this repo's recent style:
!echo "=== Staged (git diff --cached --stat) ==="; git --no-pager diff --cached --stat 2>/dev/null; echo; echo "=== Working tree (git status --short) ==="; git --no-pager status --short 2>/dev/null; echo; echo "=== Recent subjects — match this convention ==="; git --no-pager log -20 --pretty=format:'%s' 2>/dev/null
What to do
- See exactly what's being committed. Read the full staged diff with
git --no-pager diff --cached. If nothing is staged (the stat above is empty), tell me and stop — I stage changes myself; never rungit add. - Learn the repo's commit style from the recent subjects above — prefix convention (this repo
uses
[Scope] summary), imperative vs. past tense, subject length, whether bodies are used. Match what's already there; don't impose Conventional Commits / gitmoji if the repo doesn't use them. - Write the message from the actual staged diff (not a guess):
- A concise subject in the repo's style (~50 chars, imperative). Fold in my hint if given: $ARGUMENTS.
- Add a short body (wrapped ~72 cols) only when the change needs the why; otherwise subject-only. Don't invent motivation that isn't evident from the diff.
- Print the message in your reply first — as a single fenced
```textblock, copy-paste ready. This in-reply copy is the durable one: it lives in the transcript, so it survives even if the clipboard gets overwritten later (by me copying something else, or another Claude session runningwl-copy). Always print it; don't rely on the clipboard alone. - Save it to a file in the repo so I can recover it any time: resolve the path with
git rev-parse --git-path CLAUDE_COMMIT_MSG(per-worktree correct), then use the Write tool to write the raw message there — notCOMMIT_EDITMSG, which git overwrites on everygit commitbefore the editor opens. Myprepare-commit-msghook prefills the commit editor fromCLAUDE_COMMIT_MSG(one-shot) on the nextgit commit/ lazygitC. The file lives inside the git dir so it never shows up ingit status. - Also copy it to the clipboard as a convenience:
wl-copy < <path from step 5>. Then tell me all three places it is: printed above, saved toCLAUDE_COMMIT_MSG(hook prefills the next commit), and on the clipboard — so I never lose it to a stray copy. - Never run
git add,git commit, orgit push, and never offer to — I stage and commit manually. Draft only.