daily_log

Scan the current conversation thread and append a markdown entry to Work Log.md.

41|10|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill daily-log-krishnakanthb13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily_log
Source: https://github.com/krishnakanthb13/antigravity_global_skills/tree/main/daily_log
Command: npx skills add https://github.com/krishnakanthb13/antigravity_global_skills --skill daily-log-krishnakanthb13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans the current conversation thread and updates a project work log, ensuring progress is captured consistently.

Core Features & Use Cases

  • Automatically identifies and appends a concise summary of features, bugs, and decisions from the session.
  • Maintains a structured Work Log.md with timestamps to support release notes and project tracking.
  • Works across conversations and teams to preserve a single source of truth for progress tracking.

Quick Start

Append your session context to the work_log directory by running the daily_log skill on the active thread.

Frequently Asked Questions about daily_log

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically log session progress to a markdown work log?

To automatically log session progress, this Skill scans your current conversation thread and appends a concise summary of features, bugs, and decisions to a structured markdown work log with timestamps.

What is the best way to maintain a persistent work log for collaborative development sessions?

The best way to maintain a persistent work log is to automate the extraction of decisions and fixes from the conversation, appending them directly into a structured markdown file to preserve a single source of truth.

Can I use this to generate release notes from a running log of features and fixes?

Yes, you can use this to generate release notes because it maintains a structured Work Log.md with timestamps that captures features, bugs, and decisions to support project tracking.

Do I need a specific directory setup to write a markdown work log from a conversation thread?

Yes, you need to designate a specific work_log directory where the Skill writes the formatted markdown entries containing your summarized session context and timestamps.

How does automated session logging work for project tracking across teams?

Automated session logging works by scanning the active conversation, formatting a markdown entry with concise summaries and timestamps, and writing it to a shared directory to preserve a single source of truth for progress tracking.