Power Generate Linear Worklog

Generate a structured worklog from git history, PR descriptions, and commit messages, formatted for import into Linear, Jira, or other project management tools.

When to Use This Command

Run this command when...

• You need to report what was accomplished during a sprint or time period
• You want to generate a worklog from git commits for billing or client status updates
• You are preparing a retrospective and need a summary of all completed work

Avoid this command when...

• You need real-time project tracking rather than a historical report
• Your commit messages are not descriptive enough to produce a useful worklog

Quick Start

Copy
# .claude/commands/power-generate-linear-worklog.md
---
allowed-tools: ["Bash", "Read"]
---
Parse git log for the specified time range. Group commits by
feature/fix/chore. Estimate time spent. Format for import.

Example usage:

/power-generate-linear-worklog --since "2 weeks ago"

Example output:

Worklog: Mar 1 - Mar 15, 2026
==============================

Features:
  - OAuth2 login with Google provider     8h  (12 commits)
  - Dashboard chart component             4h  (6 commits)

Fixes:
  - Payment webhook timeout handling      2h  (3 commits)
  - Mobile nav menu overlap               1h  (2 commits)

Chores:
  - Dependency updates                    1h  (4 commits)
  - CI pipeline optimization              2h  (5 commits)

Total: 18h across 32 commits

Core Concepts

Concept	Description
Commit parsing	Extracts type (feat/fix/chore) from conventional commit prefixes
Time estimation	Estimates effort based on commit count and diff size heuristics
Grouping	Clusters related commits into logical work items by branch or scope
Export format	Outputs in formats compatible with Linear, Jira, or CSV import

git log --since --> Parse Commits --> Classify by Type
                                          |
                              Group Related Commits
                                          |
                              Estimate Time per Group
                                          |
                              Format for Export

Configuration

Option	Default	Description
since	1 week	Start of the time range
until	now	End of the time range
format	markdown	Output format (markdown, json, csv, linear)
author	all	Filter by specific git author email
group-by	type	How to group commits (type, branch, author)

Best Practices

1. Use conventional commits -- feat:, fix:, chore: prefixes enable reliable automatic classification.
2. Review time estimates -- estimates are heuristic and should be adjusted to reflect actual effort spent.
3. Filter by author -- in team repos, generate per-developer worklogs for individual reporting.
4. Export weekly -- shorter intervals produce more accurate worklogs than large monthly dumps.
5. Include PR descriptions -- merge commits with PR descriptions add valuable context beyond just commit messages.

Common Issues

1. Commits not classified -- commits without conventional prefixes land in an "Other" bucket. Adopt conventional commits going forward.
2. Time estimates too low -- the estimator uses diff size as a proxy for effort. Meetings, design, and review time are not captured.
3. Merge commits inflate counts -- merge commits can double-count work. Use --no-merges to exclude them from the analysis.