Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Dev Journal

    1

    Keep a journal of your work by recording changes, decisions, trade-offs and learnings in one structured Markdown file.

    Free

    Security scanned
    Dev Journal

    Dev Journal

    Example session with this skill installed

    journal this session. I refactored the auth middleware to use JWT instead of sessions because we need to scale horizontally. I skipped adding refresh tokens for now to meet the deadline.

    • Read your context and instructions
    • Compiled the dev journal

    Session recorded successfully. I have captured the refactor details, the decision regarding JWT, and the trade-off involving refresh tokens.

    dev-journal entry

    • Date: 2023-10-27 14:30
    • Session ID: 20231027-1430-a9f2
    • Project: backend-api
    • Branch: feature/jwt-auth
    • Source: manual

    Recap
    Refactored the authentication middleware to implement JWT-based state.
    Updated the request pipeline to validate tokens and extract user identity.
    Verified that horizontal scaling no longer requires session affinity.

    Decisions

    1. Decided: Switched from session-based auth to JWT.
      Why: To support horizontal scaling without shared session state.
      Gave up: The ability to easily revoke individual sessions server-side.
    2. Decided: Deferred refresh token implementation.
      Why: To meet the immediate sprint deadline.
      Gave up: Longer-lived user sessions without re-authentication.

    Trade-offs

    • Security compromise: Users cannot be logged out globally until the JWT expires since refresh tokens are missing.

    Learned

    • The existing middleware was tightly coupled to the Express session object, requiring more refactoring than initially estimated.

    Journal: file:///Users/developer/projects/backend-api/dev-journal.md (14 entries)

    Next steps

    • Click the file link above to review the formatted entry.
    • Create a ticket for the deferred refresh token implementation.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    AI makes developers incredibly more productive. The problem is that this speed leaves no trail. A week later you remember that something changed, but not what was decided, why that option won, or what you gave up to get there.

    dev-journal fixes that with one Markdown file. Ask your agent to "journal this session" and it appends an entry with the session ID, a two or three line recap of what changed, and the decisions taken: what was chosen, why, and what was given up. It also records the trade-offs the work now carries, such as debt taken on or a check skipped, and what was learned, from root causes to tool quirks a future session should know. The result is a searchable log that answers "why is it like this?" months after the conversation is gone.

    What it does

    • Recaps generates a concise three-line summary of code changes and session outcomes.
    • Decision logging records what was chosen, why, and what was sacrificed for every major implementation path.
    • Trade-off tracking captures technical debt, shortcuts, and known limitations accepted during the session.
    • Knowledge capture identifies and logs new facts about the codebase or tools learned during development.
    • Journal management supports viewing recent history and reconfiguring journal storage locations across different projects.

    How it works

    1. Add entry triggered by "journal this session" to compile metadata, decisions, and trade-offs into the Markdown file.
    2. Show entries displays the last N sessions to quickly regain context on past work.
    3. Configure location moves or resets the journal path, stored in a local JSON config for persistence across tools.

    Frameworks & tools

    This skill works via standard shell commands and local filesystem access. It integrates with git for branch tracking and resolves paths via environment variables or JSON configuration files.

    Why this beats prompting it yourself

    Manual prompting often misses the "why" behind a change or forgets to document the rejected alternatives. This skill enforces a consistent ADR-style format and automatically collects session metadata like branch names and timestamps that are tedious to type manually.

    Use cases

    • Log a complex refactor including the rationale for chosen design patterns.
    • Review the last five sessions to prepare for a daily standup or weekly report.
    • Centralize all project learnings into a single docs/DEV_JOURNAL.md file.
    • Document trade-offs made during a rapid prototyping phase for future cleanup.

    Known limitations

    Requires local file system access and basic shell utilities for full metadata capture. Does not support concurrent multi-user editing of the same journal file.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Technical Documentation.

    Requires local file system access and shell utilities. Append-only logic prevents editing or reordering existing entries. No support for concurrent multi-user writing.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 13 days ago

    • Free with an Agensi account

    Software
    Git

    Permissions

    Terminal / Shell
    Read Files
    Write Files
    Network Access
    Listed13 days ago

    What's inside

    Frequently Asked Questions

    The skill manages a single Markdown file (defaulting to `docs/DEV_JOURNAL.md`) and a local JSON configuration file. It uses these to track your journal's location and ensure entries are appended correctly across different project sessions.

    Unlike manual prompting, this skill uses a structured ADR-style (Architecture Decision Record) framework to ensure you capture not just what you did, but the rejected alternatives and technical debt incurred. It also automatically pulls metadata like Git branch names and timestamps, saving you repetitive typing.

    The skill is designed to work with any AI agent that has shell or filesystem access. It relies on standard CLI commands and environment variables, making it compatible with most modern terminal-based AI tools and IDE extensions.

    While it currently supports one journal file per project, you can use the 'Configure location' command to easily point the skill to different directories or file names as you switch between various repositories.

    No, this skill is designed for local development workflows and does not support concurrent editing. To avoid file conflicts, it is recommended for use by a single developer per project journal.

    New in Technical Documentation

    Free