القائمة
Write a journal entry documenting what was done in this session. Records what changed, why, and next steps. Saves to both SQLite and a timestamped markdown file.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Show usage information for any workflow-toolkit skill. Use when the user asks how to use a specific skill, what a skill does, or needs guidance on workflow-toolkit features. Also triggers on "help", "how do I", "what does X do", or "usage" in the context of workflow-toolkit skills.
Initialize and verify the workflow-toolkit environment. Checks SQLite availability, creates the journal database, verifies directory structure, checks gh CLI auth, and reports readiness. Run this after installing the plugin or when troubleshooting.
Pre-flight checklist for open source contributions. Validates code changes against project rules, PR size limits, commit format, linting, and type-checking. Does NOT push or create PRs — only reports issues.
Creates a new Claude Code custom subagent configuration. Guides you through designing agent scope, tools, permissions, hooks, and system prompts.
Creates a new Claude Code custom skill (slash command). Guides you through designing, writing, and placing the SKILL.md file with proper frontmatter, arguments, and best practices.
Open the journal SQLite database in a GUI viewer (DB Browser for SQLite, or similar).
| name | journal-write |
| description | Write a journal entry documenting what was done in this session. Records what changed, why, and next steps. Saves to both SQLite and a timestamped markdown file. |
| argument-hint | ["optional summary of what was done"] |
| disable-model-invocation | true |
This skill writes a structured journal entry documenting the current session's work.
If $ARGUMENTS is provided, use it as a starting point for the summary. Otherwise, reflect on what was done in the current conversation.
Compose a structured journal entry with these sections:
Generate a timestamp using date -u '+%Y-%m-%d %H:%M:%S' for the entry, and date -u '+%Y-%m-%d_%H-%M-%S' for the filename.
Insert the entry into SQLite using Bash:
TIMESTAMP=$(date -u '+%Y-%m-%d %H:%M:%S')
DB_PATH="$CLAUDE_PROJECT_DIR/.claude/journal/journal.db"
sqlite3 "$DB_PATH" "INSERT INTO entries (timestamp, type, summary, details, files_changed, next_steps) VALUES ('$TIMESTAMP', 'manual', '<SUMMARY>', '<DETAILS>', '<FILES_JSON>', '<NEXT_STEPS>');"
$CLAUDE_PROJECT_DIR/.claude/journal/entries/YYYY-MM-DD_HH-MM-SS.md with this format:# Journal Entry: YYYY-MM-DD HH:MM:SS
## Summary
<one line>
## What Was Done
- <bullet points>
## Why
<reasoning>
## Files Changed
- `path/to/file.ts` — description
## Next Steps
- <bullet points if any>