create-work-loglisted

# Create Work Log Turn real git activity into a readable work log — Markdown, because the destination is typically an Obsidian vault or a chat paste, not a browser. ## 1. Resolve config Read `config.json` next to this SKILL.md. If it doesn't exist, read [config.example.json](config.example.json) for the shape, ask the user for real values, then write `config.json` (git-ignored): - `repos` — absolute paths of repositories to scan. - `outputDir` — where logs are saved (e.g. an Obsidian vault folder). - `gitAuthor` — optional; a `git log --author` filter. When omitted, use each repo's `git config user.name`. ## 2. Determine the period Default: today (`--since 00:00`). "Weekly" or an explicit range from the user overrides it. State the resolved period in the log header. ## 3. Collect activity — from git, not memory Per configured repo: - `git log --all --author=<author> --since=<start> --until=<end> --pretty='%h %s (%D)'` for commits (all branches — feature-branch work counts). - `git status --short` for uncommitted work in progress, noted as such. - Skip repos with no activity; list them in one "no activity" line at the end. Completion criterion: every configured repo was scanned; nothing in the log is inferred without a commit or a dirty file behind it. ## 4. Compose the log Group by repo, then by theme (feature/fix/docs — the Conventional Commit prefixes make this mechanical). Write prose summaries in the user's conversation language; keep commit subjects verba