Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
How this skill is triggered — by the user, by Claude, or both
Slash command
/smartbuddy:buddy-journalThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The buddy's state file path is in your context under `[SMARTBUDDY_FULL_STATE]` (the "State file:" line). The journal lives alongside it at `{state_dir}/projects/{project_hash}/journal.md`. Read that file to display entries chronologically.
The buddy's state file path is in your context under [SMARTBUDDY_FULL_STATE] (the "State file:" line). The journal lives alongside it at {state_dir}/projects/{project_hash}/journal.md. Read that file to display entries chronologically.
If no journal exists, explain that the buddy writes journal entries when it selects the "journal" action during coding sessions — this happens naturally as the buddy's personality develops.
npx claudepluginhub tucuxi-inc/smartbuddyAutomates daily development logging: summarizes progress, writes project-isolated diary entries in Markdown, and supports syncing to Notion or Obsidian. Keeps context across multiple projects.
Generates markdown developer journals from Claude Code activity data over specified time periods like today or last week. Focuses on accomplishments, decisions, and project progress with day-by-day breakdowns.
Writes and maintains implementation diaries for non-trivial tasks like features, bug fixes, refactors; captures changes, why, successes, failures with errors/commands, learnings, tricky parts, review notes in dated Markdown files.