skills.rest
aroido
aroidoOFFICIAL
Explore all skills by this author →
WebsiteGitHub

command-daily-log

Generate a daily work log from Git commits and GitHub issues into WORK_LOG.md.

Updated Apr 22, 2026
Search Tags:#automation#git#developer tools#github#daily report#log
One-click install
npx skills add https://github.com/aroido/vibesmith --skill command-daily-log
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: command-daily-log
Source: https://github.com/aroido/vibesmith/tree/main/.codex/skills/command-daily-log
Command: npx skills add https://github.com/aroido/vibesmith --skill command-daily-log

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the creation of a daily work log, consolidating your recent activities and commitments.

Core Features & Use Cases

  • Consolidates Git Commits: Gathers your commits from the current day.
  • Tracks GitHub Issues: Lists your open and recently closed GitHub issues.
  • Generates Structured Log: Formats collected information into a readable WORK_LOG.md file.
  • Use Case: At the end of each workday, run this command to quickly generate a summary of your progress, commits, and issue status for reporting or personal tracking.

Quick Start

Run the command /daily-log to generate your daily work log.

Frequently Asked Questions about command-daily-log

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

FAQPage Schema
How do I automate my daily work log from Git commits and GitHub issues?▼

You can generate a daily work log by running the command, which automatically collects your current Git commits, open GitHub issues, and recently closed issues into a structured markdown file at `docs/WORK_LOG.md`.

What is the best way to generate a daily developer report from GitHub activity?▼

The best way to generate a daily developer report is to consolidate your Git commit history and GitHub issue status into a structured markdown file, providing a quick summary of your daily progress for reporting.

Do I need the gh CLI installed to track GitHub issues in my daily log?▼

Yes, you need the `gh` CLI installed and configured, as this skill depends on it to fetch your open and recently closed GitHub issues for daily work log generation.

Can I use this to create a markdown work log for software engineering progress tracking?▼

Yes, you can use this to create a markdown work log for software engineering progress tracking, as it formats your Git commits and GitHub issues into a readable `WORK_LOG.md` file at the end of each workday.

What information does the daily work log include from my repository?▼

The daily work log includes your Git commits from the current day, open GitHub issues, and recently closed GitHub issues, formatted into a structured markdown file for reporting and personal tracking.

When should I run the daily work log generation command?▼

You should run the daily work log generation command at the end of each workday to quickly summarize your progress, commits, and GitHub issue status for reporting or personal tracking purposes.

Related Skills

Explore More Software Engineering Skills→
Strategic-AutomationStrategic-Automation
6

github-auth

Configure GitHub authentication via HTTPS tokens, SSH keys, or gh CLI.

Official
Intermediate
zm2231zm2231

project-status

Generate project status reports with milestones, metrics, and risk scores.

Community
Advanced
adeboldadebold

github-project-management

Orchestrate swarm-coordinated GitHub issue management and project-board automation.

Community
Intermediate
meaganewallermeaganewaller
3

Standup Skill

Aggregate developer activity logs and GitHub pull request data into a daily standup report.

Community
Intermediate