Menü
Capture notes into your daily journal using the jrnl CLI
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Create a Google Task via the IFTTT JSON webhook
Create a git commit using the message format below
Split working tree changes into up to five atomic commits, each with a message generated using the git-commit skill
Use Bun's shell API ($ from "bun") when writing or editing scripts that run shell commands in src/. Use when adding or changing subprocess/shell usage under src/, or when the user asks for shell execution in this project. Prefer Bun Shell over child_process or execSync.
Polish text by refining clarity, coherence, and conciseness
Add GitHub Actions workflow for publishing Rust crates using trusted publishing (OIDC). Use when setting up automated crate publishing, configuring crates.io trusted publishing, or when the user mentions crate publishing workflow.
| name | jrnl |
| description | Capture notes into your daily journal using the jrnl CLI |
Use the jrnl CLI to append entries to your daily journal. The journal is a
Markdown file named Journal YYYY-MM-DD.md stored in ~/Dropbox/Brain/journal/,
~/Brain/journal/, or ~/.journal/ (first found wins).
jrnl <title> — Read stdin and append a timestamped entry with the given title.
Prefer a temp file or HEREDOC for the body to avoid escaping issues:
cat <<'EOF' | jrnl "Auth refactor"
Finished refactoring the auth module.
Notes with "quotes" and $vars stay literal.
EOF
# or write body to a temp file, then:
jrnl "Auth refactor" < /tmp/jrnl-body.md
jrnl -c <title> — Same as above, but reads the body from the clipboard
instead of stdin.
jrnl -e — Open today's journal file in $EDITOR (defaults to nvim). The
file is created with a template if it doesn't exist.
jrnl -p — Print the path to today's journal file and exit.
Entries are appended under an h3 heading (### HH:MM <title>). Format the body
in Markdown. Because each entry starts at h3, use h4 (####) or deeper for any
headings within the body.