What problem does it solve? Solo developers often lose track of what they did on a given day and must manually write progress logs. This Skill reads git commit history (read-only) for a chosen period and automatically reflects it into a dated project progress log, so the record of "what was done when" is kept without manual writing. ## Core Features & Use Cases - Period-based commit collection: Accepts a date range argument (yesterday, today, or an explicit range like 2026-07-10..2026-07-13) and gathers commits via read-only git log/git fetch. - Idempotent log appending: Appends commits to docs/00_관리/진행로그.md under date sections, skipping commits whose SHA already appears in the log so re-runs never duplicate entries. - Commit prefix parsing: Classifies Conventional Commits (feat:, fix:, etc.) and bracket tags ([TSK-12]) to summarize counts by type and link to tracking keys. - Commit safety protocol: Guides users to check git status, use targeted git add, and abort on unexpected deletions—protecting against phantom mass deletions caused by cloud-sync folders (e.g., iCloud Drive) corrupting the git index. - Use Case: At the start of a work session, ask for a summary of yesterday's commits; the Skill collects them, appends them to the progress log, and reports a short digest with per-type counts. ## Quick Start Ask the assistant to summarize yesterday's git commits and add them to the project progress log.
