Journal This
BlueFenixProductions/journal-this
Converta sessões de trabalho em entradas de diário automaticamente
Ver no GitHubSkill para Claude Code que transforma uma sessão de trabalho em entrada de diário datada, escrita na sua voz pessoal e salva em pasta local ou repositório GitHub. Lê o histórico da conversa, identifica o que realmente avançou e gera um registro estruturado mantendo seu estilo de escrita.
Instalação
npx convez-ai BlueFenixProductions/journal-this1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Manter um diário técnico de projetos e aprendizados
- Documentar sessões de engenharia com contexto pessoal
- Criar histórico de decisões e progressos em repositório versionado
Veredito

Ferramenta bem executada para quem mantém diário técnico. Integração direta com GitHub e suporte a voz pessoal via análise de entradas anteriores é diferencial. Instalação simples e fluxo intuitivo, ideal para engenheiros que querem documentação sem fricção.
README
A tradução para o português deste README ainda está na fila.
journal-this
A Claude Code skill that turns the current session into a dated markdown journal entry, written in your voice, saved to your journal (a local folder or a GitHub repo).
It's the generalized, shareable version of a personal engineering-journal workflow: read the conversation, find what actually moved, write it up the way you'd write it, and file it (commit + push for GitHub destinations, handling the multi-machine pull–rebase race).
Install
One line from a clone:
git clone https://github.com/BlueFenixProductions/journal-this
cd journal-this
./install.sh # -> ~/.claude/skills/journal-this (Claude Code)
./install.sh --codex # -> ~/.agents/skills/journal-this (Codex)
Then reload Claude Code (/reload-plugins, or restart) and type /journal-this.
Prefer to do it by hand? It's a single folder — copy it in:
cp -R skills/journal-this ~/.claude/skills/journal-this
That's the whole skill: SKILL.md plus a config template.
Use
Type /journal-this (or just say "journal this") at the end of a work session — it also offers to journal proactively when a substantial session winds down.
- First run walks you through a one-time setup interview: your name, where your existing writing lives (so it learns your voice), and where entries should go. It saves your answers to
~/.config/journal-this/config.json. - Every run after that reads that config, anchors on a couple of your recent entries, writes the new entry, and files it.
Re-run the interview any time with /journal-this setup.
Example
First run — the setup interview:
You: /journal-this
Claude: No config yet — let's set up your journal (takes 30 seconds).
1. Whose journal is this? → Dana
2. Where does your existing writing live, so I can match your voice?
(local folder / GitHub repo / paste / none) → ~/devlog/entries
3. Save entries to a plain folder or a GitHub repo? → GitHub repo
• local clone path? → ~/devlog
• subdirectory? → entries
• branch / remote? → main / origin
• push directly or open a PR? → directly
4. Filename pattern? → (default) YYYY-MM-DD-kebab-slug.md
5. Add a co-author trailer to commits? → default Claude trailer
Saved to ~/.config/journal-this/config.json. You're set — next time
just say "journal this".
Every run after that — journaling a session:
You: journal this
Claude: Read your 2 most recent entries to anchor voice.
Wrote: ~/devlog/entries/2026-06-07-oauth-token-refresh-race.md
Commit a1b9f3c → pushed 4e21d0a..a1b9f3c main -> main
The entry comes out in your voice and house style (it reproduces the frontmatter, headings, and structure your existing entries use), summarizing what actually moved in the session — what shipped, what broke, what's deferred — not a generic recap.
What's in the box
install.sh # one-line installer (copies the skill into your skills dir)
skills/
journal-this/
SKILL.md # the skill itself — the only file an install needs
config.template.json # documents every config field; setup creates the real one
CHANGELOG.md
CONTRIBUTING.md
LICENSE
Versioning & contributing
Releases follow Semantic Versioning; see CHANGELOG.md. Contributions welcome — see CONTRIBUTING.md. Curious how this was designed? The spec lives in docs/superpowers/specs/ — note those design docs describe an earlier plugin-packaging approach that was later simplified to this plain skill.
License
MIT — see LICENSE.