How this command is triggered — by the user, by Claude, or both
Slash command
/claude-journal:journal-addThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Add Journal Entry
You are helping the user add a journal entry.
## Process
1. **Gather information:**
- **Title** (required): Ask for a brief title
- **Description** (required): Ask for 1-2 sentence description
- **Project** (optional): Ask if this is related to a specific project/repo
- If user is in a git repo, suggest using the repo name
- If not specified, can be left empty
- **Tags** (optional): Suggest relevant tags based on the content
- Technical terms mentioned
- Type of work (feature, bugfix, refactor, etc.)
- Technologies used
2. **Use t...You are helping the user add a journal entry.
Gather information:
Use the MCP tool:
Call journal_add with the gathered information:
journal_add(
title="User's title",
description="User's description",
project="project-name" (if provided),
tags=["tag1", "tag2"] (if provided)
)
Confirm success: Tell the user their entry was saved and show the ID for reference.
Example 1: Simple entry
Example 2: Bug fix
npx claudepluginhub chrismbryant/claude-journal-mcp --plugin claude-journal/soul-journalAppends the provided entry text to today's Markdown journal file for the current project, creating the daily file and updating project index if needed.
/diaryCreates or updates today's session diary entry in /design-intent/diary/session-YYYY-MM-DD.md documenting accomplishments, decisions, current state, priorities, and issues.
/logLogs orchestrated task work including time spent, progress notes, and code stats to tools like Linear, Obsidian, Jira, or GitHub Issues. Supports task ID and destination options.