aboutsummaryrefslogtreecommitdiff
path: root/inbox
Commit message (Collapse)AuthorAgeFilesLines
* chore(inbox): cross-machine handoff from work re: mid-session log disciplineCraig Jennings2026-05-181-0/+30
|
* docs(commits): check disk before declaring /review-code unavailableCraig Jennings2026-05-183-223/+0
| | | | | | | | Step 1 told the agent to run /review-code but didn't say what to do when the skill exists on disk yet isn't in the session's available-skills list. The list covers plugin-installed skills only. User commands under ~/.claude/commands/ are routable as slash-commands but don't appear in it, so the agent could declare /review-code unavailable and fall through to the trivial-one-liner exception in Step 2. The new Discovery check tells the agent to verify both ~/.claude/commands/review-code.md and ./.claude/commands/review-code.md on disk before declaring the skill unavailable, and surface the mismatch rather than auto-skipping. Also drops three absorbed or stale inbox files: the skill-discovery handoff (signal absorbed by this edit), the missing-inbox-dir handoff (already resolved by 470085f), and a stale date-coverage scan output (deferred until the task-review habit lands).
* docs(inbox): Add handoffs on skill discovery and missing inbox dirCraig Jennings2026-05-172-0/+193
|
* chore(ai): archive session record and wrap-up lint followupsCraig Jennings2026-05-171-0/+15
|
* chore(ai): archive session record and wrap-up lint followupsCraig Jennings2026-05-161-0/+15
| | | | Records today's task-review spec + google-keep MCP install work. Lint-followups carries one misplaced-heading judgment (line 2153, false positive — `**` inside `=...=` verbatim) and a 9-entry date-coverage list, both deferred per the task-review spec's plan to retire the date-coverage scan once implemented.
* chore(inbox): track inbox/ with a .gitkeep so it persists across sessionsCraig Jennings2026-05-161-0/+0
|
* chore(inbox): remove sync-child-priority spec — implementedCraig Jennings2026-05-141-69/+0
|
* docs(respond-to-cj-comments): add no-cj-token-in-replies rule + ↵Craig Jennings2026-05-141-0/+69
child-priority-sync spec Skill update: refer to processed items as "cj comments" in chat replies, summaries, and todo.org entries — never write the literal token in my output. The reason is search hygiene: Craig greps his files for the token to find pending annotations, and noise from my replies clutters that. Spec drop into inbox/: child-priority-sync-todo-cleanup.md captures the implementation recommendation for adding --sync-child-priority to todo-cleanup.el plus four open questions (sync direction, opt-out mechanism for deliberately-lower children, auto-apply vs --check, no-priority-parent edge case) Craig needs to answer before wiring it in.