From daily
Evening wind-down, the pair of /morning. On "evening" (or "/evening", "на сегодня хватит", "чем закончить день", "подведи итог дня") close the work day: summarize what was done TODAY, name what can wait until tomorrow, and suggest how to spend the evening well: physical activity, mental recovery, and one or two people worth talking to. Use whenever the user asks for an end-of-day summary or signals fatigue in the evening.
How this skill is triggered — by the user, by Claude, or both
Slash command
/daily:eveningThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The job: give an honest "you did enough today", park the work cleanly, and
The job: give an honest "you did enough today", park the work cleanly, and point the evening at recovery, not more screens. Tone: warm, brief, zero guilt. English.
TODAY=$(date +%Y-%m-%d)
# commits today across every repo under ~/Documents/Work/Projects
find ~/Documents/Work/Projects -maxdepth 4 -name .git -type d 2>/dev/null
git -C <repo> log --all --since="$TODAY 00:00" --pretty='%h %s' 2>/dev/null
Plus today's Claude Code sessions (~/.claude/projects/*.jsonl modified
today) and memory notes. Compress into 3-5 lines of real accomplishment;
name finished things as finished. If the day was mostly thinking/debugging
with no commits, say that it still counts.
git status -s per active repo), a half-applied migration, a prod
deploy mid-flight. If something shouldn't be left overnight, name ONLY
that as the one thing to close out.Check the calendar for tonight/tomorrow morning (Google Calendar tools if connected: events between now and tomorrow 10:00) so suggestions fit reality (don't propose a workout at 22:30 before an 8:00 event).
Suggest ONE physical and ONE mental item, varied across days, e.g.:
If a wellbeing tracker/notes exist (e.g. Jarvis wellbeing), align with it rather than inventing a parallel plan.
Suggest 1-2 people to reach out to tonight, sourced from real signals, in priority order:
🌆 Evening check-out — <date>
**Done today:** <3-5 lines>
**Park it:** <the one thing to close, or "nothing dangling: safe to stop">
**Tomorrow:** 1) ... 2) ... 3) ...
**Tonight:** <one physical + one mental suggestion, one line each>
**Reach out:** <1-2 people and why>
Работы на сегодня хватит. 🙂
Keep the whole thing under 20 lines. Never add new work items in the evening; anything new goes into tomorrow's list.
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
npx claudepluginhub kulykivska/claude-plugins --plugin daily