skills.rest
zjh08177
zjh08177COMMUNITY
Explore all skills by this author →
GitHub

work-log

Aggregate Git, review, vault, and memory signals into a structured weekly work log.

Updated Aug 27, 2026
Search Tags:#productivity#memory#weekly-report#work-log#git-commits#signal-gathering#vault-artifacts
One-click install
npx skills add https://github.com/zjh08177/agent-harness --skill work-log-zjh08177
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: work-log
Source: https://github.com/zjh08177/agent-harness/tree/main/skills/work-log
Command: npx skills add https://github.com/zjh08177/agent-harness --skill work-log-zjh08177

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Friday weekly work log compilation is manual and time-consuming. This skill automatically gathers signals from Git commits, merged MRs, code reviews, vault artifacts, auto-memory, and the daily scratch file to draft a ready-to-review weekly entry.

Core Features & Use Cases

  • Auto-gathers signals across repos, MRs, reviews, vault artifacts, memories, and today’s scratch to draft a weekly entry.
  • Produces a structured weekly log with sections for Shipped, Invisible Work, Learned, and Carry-forward, ready for user review.
  • Useful for weekly planning, performance reviews, and personal productivity tracking.

Quick Start

Ask the AI to generate this week's work log using signals from commits, MRs, vault artifacts, memories, and today’s scratch file.

Frequently Asked Questions about work-log

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

FAQPage Schema
How do I automatically generate a weekly work log from git commits and vault artifacts?▼

You can auto-compile a weekly work log by gathering signals from git commits, code reviews, vault artifacts, and daily scratch notes. This produces a structured markdown file with sections for shipped items, invisible work, and carry-forward tasks.

What is the best way to track invisible work for my weekly report?▼

Tracking invisible work for a weekly report involves aggregating signals from code reviews, auto-memory, and vault artifacts. This captures non-shipped contributions and drafts them into a dedicated invisible work section for your review.

Can I draft a performance review from my git commits and daily notes?▼

Yes, you can draft a performance review by aggregating git commits, merged MRs, and daily notes into a structured weekly work log. This creates a historical record of shipped features and learned concepts useful for tracking personal productivity.

Do I need configured repos and vault paths to compile a weekly work log?▼

Yes, you need access to configured repos, vault paths, memory directories, and a daily scratch file. The work log compilation requires these sources to gather signals and output a ready-to-review markdown file under Areas/Career/work-log.

How does signal gathering work for automated weekly reporting?▼

Signal gathering for automated weekly reporting works by scanning version control commits, merged MRs, code reviews, and vault artifacts. It extracts relevant activity data and structures it into Shipped, Invisible Work, Learned, and Carry-forward sections.

Related Skills

Explore More Personal & Entrepreneur Skills→
ronnycodingronnycoding
12

daily-briefing

Aggregate calendar events, email inbox status, and reminders into a structured daily briefing.

Community
Intermediate
hemoryhemory

career-setup

Initialize a career development system with Markdown files for job descriptions, reviews, and goals.

Community
Intermediate
frankxaifrankxai
6

memory/capture-discipline

Define daily capture and routing rules for personal knowledge management systems.

Community
Intermediate
wwsunwwsun
1

daily-progress

Summarize git commit histories into structured daily or weekly work reports.

Community
Intermediate