Can I use this on a project that already has a long history?

Yes, the skill includes a reconstruction command that can parse your git history (especially conventional commits) to build a historical worklog automatically.

Where is the worklog data stored?

The data is stored in a standardized Markdown file at `.devloop/worklog.md`, which is intended to be committed to your repository.

How does the worklog differ from a development plan?

The plan is a dynamic document for active and pending tasks, whereas the worklog is a permanent, immutable history of completed work linked to specific git commits.

Is the worklog updated automatically?

The skill defines triggers for automatic updates after successful commits, as well as manual prompts for phase and feature completion.

Devloop Worklog Management

Name: Devloop Worklog Management
Author: Zate

byZate

Productividad y Flujo de Trabajo

Maintains a structured, permanent history of completed work by mapping specific tasks to git commits.

Acerca de

The Devloop Worklog Management skill provides a robust framework for documenting project progress separate from active planning. It bridges the gap between raw git history and high-level task management by maintaining a commit-linked audit trail of every feature and fix. This skill allows Claude to automatically update logs after commits, generate comprehensive session summaries, and even reconstruct history for existing projects. By using this standardized format, teams can easily generate release notes, onboard new developers with clear context, and maintain a source of truth for project evolution.

Características Principales

Structured versioning and feature-based sectioning
Session summary generation using historical context
0 GitHub stars
Automatic post-commit updates mapping tasks to git hashes
Integration with active plans to track work transition
Historical work reconstruction from existing git logs

Casos de Uso

Generating accurate release notes and changelogs from completed tasks
Providing historical context for onboarding or session resumes
Auditing project progress by linking specific code changes to original requirements

Acerca de

Características Principales

Structured versioning and feature-based sectioning
Session summary generation using historical context
0 GitHub stars
Automatic post-commit updates mapping tasks to git hashes
Integration with active plans to track work transition
Historical work reconstruction from existing git logs

Casos de Uso

Generating accurate release notes and changelogs from completed tasks
Providing historical context for onboarding or session resumes
Auditing project progress by linking specific code changes to original requirements