Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Local DevLog MCP

    1

    Turn local Git push activity into a reviewable daily dev log, then publish only the exact version you explicitly approve.

    Free

    Security scanned
    Local DevLog MCP

    Local DevLog MCP

    Example session with this skill installed

    Summarize my git activity for 2024-05-20 and save it as a draft.

    • Read your context and instructions
    • Compiled the local devlog mcp

    I have retrieved your Git activity for May 20th, 2024, across 2 repositories. A new draft has been created with draftId: <<UUID>>.

    Daily DevLog Draft: 2024-05-20

    Status: Draft (Unapproved)
    Timezone: America/Los_Angeles
    Version: 1

    Activity Summary

    RepositoryBranchEventStatusCommit Subject
    api-servicefeat/auth-fixPush AttemptREMOTE_MATCHfix: resolve jwt token expiration edge case
    api-servicefeat/auth-fixPush AttemptREMOTE_MATCHtest: add unit tests for auth middleware
    frontend-uimainPush AttemptUNCONFIRMEDdocs: update readme with deployment steps

    Source Warnings

    Unconfirmed Activity: The push to frontend-ui was captured locally but could not be verified against the remote origin. This may be due to a network failure or a pending push.

    • Verification Fingerprint: <<SHA-256>> String

    Next steps

    1. Please review the UNCONFIRMED entry for frontend-ui.
    2. Please review this exact draft version. I will call the approval tool only after you explicitly confirm that you approve the displayed draftId and version.
    3. Once approved, we can preview the publication to your Notion Work Log.

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

    About this skill

    Context switching and manual time-tracking drain developer focus. This skill automates the creation of daily work logs by converting local Git push attempts into structured, reviewable drafts. It ensures your activity reports are based on technical evidence rather than memory.

    What it does

    • Evidence-based drafts: Converts captured Git event IDs, branch names, and commit subjects into a cohesive daily summary.
    • Verification mapping: Identifies work as REMOTE_MATCH or unconfirmed based on remote repository states.
    • Version control: Manages draft versions with unique draftId identifiers to track changes before finalization.
    • Multi-target publishing: Syncs approved logs to Notion databases and Apple Calendar events via MCP tools.
    • State management: Maintains IANA timezone and workDate consistency across multiple repositories.

    How it works

    1. Gather activity: Call get_daily_activity to retrieve fingerprints and event logs for a specific date.
    2. Drafting: Create a daily development draft including source warnings and verification states.
    3. Review: Present the saved content to the user for explicit approval of a specific draftId and version.
    4. Publishing: Trigger previews for Notion or Calendar, followed by a final confirmation to execute the write.

    Frameworks & tools

    This skill requires the Local DevLog MCP server and its associated tools. It interacts with local Git configurations and external APIs for Notion and Apple Calendar.

    Why this beats prompting it yourself

    Prompting alone cannot verify local Git push attempts against remote states or maintain the strict state machine required for "approve-then-publish" workflows. This skill enforces a human-in-the-loop audit trail, preventing fabricated or unverified work records from reaching your production calendars or project management tools.

    Use cases

    • Summarize Git activity across multiple local repositories for a daily standup.
    • Generate an evidence-based work log for a Notion-based project tracker.
    • Create one all-day Apple Calendar summary for the approved daily development log without estimating working hours.
    • Review and refine unconfirmed Git events before finalizing a daily report.

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

    Requires Local DevLog MCP to be installed and connected to a compatible MCP client. Git push attempts are collected even while the MCP server is not running. It cannot verify work if the remote lookup fails or if history is truncated.

    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 9 days ago

    • Free with an Agensi account

    Mac only

    Software
    Local DevLog MCP 0.5.0+GitNode.js 20.19+pnpm 10.15.0

    Use an MCP client that supports stdio, such as Codex, Claude Code or Claude Desktop.

    Permissions

    Network Access
    Read Files

    - Local DevLog MCP — required local MCP server; use `https://github.com/Kyoungwoong/report_local_mcp` as the Other tool URL if the form accepts a repository URL. - Notion — optional; select only if Agensi allows optional-service wording. - Apple Calendar — optional local macOS service; describe it in Notes if it is not available in the service selector.

    Listed9 days ago

    What's inside

    Frequently Asked Questions

    This skill bridges the gap between your terminal and your project management tools by turning raw Git metadata into structured, verifiable work logs, eliminating the need for manual time-tracking and memory-based reporting.

    The skill is compatible with any AI agent or platform that supports the Model Context Protocol (MCP), including Claude Desktop and other MCP-enabled IDEs or environments.

    The skill uses a 'human-in-the-loop' workflow where it first generates a draft and assigns it a unique version ID, allowing you to review and approve the content before any data is written to Notion or Apple Calendar.

    Yes, the skill is designed to gather activity from multiple local repositories simultaneously, consolidating disparate Git events into a single, unified daily report based on your specified IANA timezone.

    While the skill automates the heavy lifting, you will need the Local DevLog MCP server installed and active local Git configurations to allow the agent to fetch your commit history and push attempts.

    New in Workflow Automation

    Free