@kairyou/agent-tools 0.11.0 → 0.12.0

package/config.default.jsonc

@@ -19,14 +19,15 @@
 
   // Optional blocks below: uncomment every line of a block, including its leading comma.
 
-  // at-self-eval, at-daily-log: default projects (otherwise just the current repo)
+  // at-self-eval, at-daily-log: default projects (otherwise just the current repo).
+  // Optional prompt: free text that tunes how that project is summarized.
   // , "workProjects": [
   //   "C:\\projects\\project-a",
-  //   "C:\\projects\\project-b"
+  //   { "path": "C:\\projects\\project-b", "prompt": "refer to `phoenix` as `Shop App` in the output; skip commits starting with `test:`" }
   // ]
 
   // at-daily-log: default file when asked to record; at-self-eval reads it as fallback
   // , "dailyLog": {
-  //   "output": "C:\\projects\\todo.md"
+  //   "output": "C:\\projects\\daily-log.md"
   // }
 }

package/docs/en/extras.md

@@ -19,13 +19,13 @@ Usage:
 - `/at-self-eval summarize July for C:\projects\project-a and C:\projects\project-b` — only those projects
 - `/at-self-eval also include C:\projects\project-c` — add to the default scope
 - Paste a daily/weekly log, or give a file path, to add business context
-- `/at-self-eval summarize from C:\projects\todo.md only` — log only, Git is not read
+- `/at-self-eval summarize from C:\projects\daily-log.md only` — log only, Git is not read
 
 Review the generated result before use.
 
 ## at-daily-log
 
-Summarize the day's Git activity across projects into a daily work log.
+Summarize each day's Git activity across projects into a daily work log.
 
 ```bash
 npx -y skills@latest add kairyou/agent-tools --skill at-daily-log -g -y
@@ -35,11 +35,12 @@ Usage:
 
 - `/at-daily-log` — print today's log
 - `/at-daily-log 2026-07-31` — pick the date
+- `/at-daily-log last week` / `/at-daily-log the last two weeks` — one entry per active day, empty days skipped
 - `/at-daily-log summarize today for C:\projects\project-a` — only that project
 - `/at-daily-log also include C:\projects\project-c` — add to the default scope
 - `/at-daily-log record the log` — record to the configured file; rerunning a day only refreshes the generated part
-- `/at-daily-log record it to C:\projects\todo.md` — record to that file
-- `/at-daily-log record every workday at 18:00` — guides you through an OS scheduled task
+- `/at-daily-log record it to C:\projects\daily-log.md` — record to that file
+- `/at-daily-log record daily at 18:00` — guides you through an OS scheduled task; days without commits are not written
 
 Review the generated result before use.
 
@@ -49,15 +50,16 @@ All in `~/.agent-tools/config.jsonc`:
 
 ```jsonc
 {
-  // at-self-eval, at-daily-log: default projects (otherwise just the current repo)
+  // at-self-eval, at-daily-log: default projects (otherwise just the current repo);
+  // prompt: free text that tunes how that project is summarized
   "workProjects": [
     "C:\\projects\\project-a",
-    "C:\\projects\\project-b"
+    { "path": "C:\\projects\\project-b", "prompt": "refer to `phoenix` as `Shop App` in the output; skip commits starting with `test:`" }
     // "C:\\projects\\temporarily-disabled"
   ],
   // at-daily-log: default file when asked to record; at-self-eval also reads it as fallback
   "dailyLog": {
-    "output": "C:\\projects\\todo.md"
+    "output": "C:\\projects\\daily-log.md"
   }
 }
 ```

package/docs/zh-CN/extras.md

@@ -18,13 +18,13 @@ npx -y skills@latest add kairyou/agent-tools --skill at-self-eval -g -y
 - `/at-self-eval 统计 C:\projects\project-a 和 C:\projects\project-b 的 7 月工作` — 只统计指定项目
 - `/at-self-eval 另外包含 C:\projects\project-c` — 在默认范围上追加
 - 可粘贴日报或周报文本, 也可提供文件路径补充业务背景
-- `/at-self-eval 只根据 C:\projects\todo.md 总结` — 只凭日志生成, 不读 Git
+- `/at-self-eval 只根据 C:\projects\daily-log.md 总结` — 只凭日志生成, 不读 Git
 
 生成的结果请人工核对.
 
 ## at-daily-log
 
-汇总一天内各项目的 Git 活动, 生成工作日报.
+按天汇总各项目的 Git 活动, 生成工作日报.
 
 ```bash
 npx -y skills@latest add kairyou/agent-tools --skill at-daily-log -g -y
@@ -34,11 +34,12 @@ npx -y skills@latest add kairyou/agent-tools --skill at-daily-log -g -y
 
 - `/at-daily-log` — 输出今天的日报
 - `/at-daily-log 2026-07-31` — 指定日期
+- `/at-daily-log 上周` / `/at-daily-log 最近两周` — 范围内每天一条, 跳过没有提交的日子
 - `/at-daily-log 统计 C:\projects\project-a 今天的工作` — 只统计指定项目
 - `/at-daily-log 另外包含 C:\projects\project-c` — 在默认范围上追加
 - `/at-daily-log 记录日报` — 记录到配置的文件; 同一天重复执行只更新生成的部分
-- `/at-daily-log 记录到 C:\projects\todo.md` — 记录到指定文件
-- `/at-daily-log 每个工作日 18:00 自动记录` — 引导搭建系统定时任务
+- `/at-daily-log 记录到 C:\projects\daily-log.md` — 记录到指定文件
+- `/at-daily-log 每天 18:00 自动记录` — 引导搭建系统定时任务; 没有提交的日子不会写入
 
 生成的结果请人工核对.
 
@@ -48,15 +49,16 @@ npx -y skills@latest add kairyou/agent-tools --skill at-daily-log -g -y
 
 ```jsonc
 {
-  // at-self-eval, at-daily-log: 默认统计的项目(不配则只统计当前项目)
+  // at-self-eval, at-daily-log: 默认统计的项目(不配则只统计当前项目);
+  // prompt: 该项目的提示词, 用来优化生成的日报和总结
   "workProjects": [
     "C:\\projects\\project-a",
-    "C:\\projects\\project-b"
+    { "path": "C:\\projects\\project-b", "prompt": "输出里把 `phoenix` 称作 `商城App`, 跳过 `test:` 开头的提交" }
     // "C:\\projects\\temporarily-disabled"
   ],
   // at-daily-log: 记录日报的默认文件; 未提供日志时 at-self-eval 也读它作补充
   "dailyLog": {
-    "output": "C:\\projects\\todo.md"
+    "output": "C:\\projects\\daily-log.md"
   }
 }
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kairyou/agent-tools",
-  "version": "0.11.0",
+  "version": "0.12.0",
   "description": "Reusable Agent Skills, plus integrations (statusline, provider usage, vision) that install into Codex, Claude Code, and opencode.",
   "license": "MIT",
   "repository": {

package/skills/workflow/at-daily-log/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: at-daily-log
-description: "Summarize one day's Git activity into a concise daily work log. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required."
-argument-hint: "[<date>]"
+description: "Summarize each day's Git activity into a concise daily work log, for a single date or a range. Uses the current repository, optional configured work projects, or paths named in conversation; configuration is never required."
+argument-hint: "[<date>|<range>]"
 ---
 
 # Daily Work Log
@@ -10,10 +10,13 @@ argument-hint: "[<date>]"
 
 ## Date and evidence scope
 
-Default to today. Accept plain-language dates or `YYYY-MM-DD`; query through the next
-day because Git's `--until` boundary is exclusive. State the resolved date.
+Default to today. Accept plain-language dates or ranges (`2026-07-31`, yesterday, last
+week, this month) and normalize to `[from, to]`; query through `<to + 1 day>` because
+Git's `--until` boundary is exclusive. State the resolved date or range.
 
-Read optional `workProjects` from `~/.agent-tools/config.jsonc`.
+Read optional `workProjects` from `~/.agent-tools/config.jsonc`. An entry is a path
+or `{ "path", "prompt" }`, where the prompt is free text this skill follows for that
+project, such as how to label items or which commits to skip.
 
 - No project named: current Git repository plus configured projects.
 - Projects named directly: only those projects.
@@ -36,35 +39,41 @@ by hash.
 Collect non-merge commits for the resolved author and day. Use subjects and changed
 paths to turn related commits into concrete completed work items. Fold formatting,
 version bumps, and follow-up fixes into the outcome they supported; do not inflate one
-change into several deliverables.
+change into several deliverables. Never restate a
+commit subject as the work item; describe the outcome it produced. A day left with
+nothing has no reportable activity.
 
 Use file counts and added/deleted lines only when they meaningfully support the work
 item. Generated files, lockfile churn, renames, and bulk formatting often make those
 numbers misleading. Metrics are evidence, never hours, difficulty, impact, or a
 productivity score.
 
-Current uncommitted changes may be shown separately as **in progress**, but never as
-proof of work on a past date. User-provided non-code work must remain clearly identified
-as user context.
+Uncommitted changes are not work items. At most, note them factually in a chat draft
+for today (project and files, no invented progress); never write them to the file:
+their dates are unverifiable, and a project left dirty for weeks would reappear as in
+progress every day. User-provided non-code work must remain clearly identified as user
+context.
 
 ## Output
 
-Match the user's language and omit empty sections:
+Match the user's language:
 
 ```markdown
 + 2026-07-31
-  完成 2 项:
   1. agent-tools: 完成多项目日报规则和 skill 落地.
   2. vscode-plugin: 修复 Webview 刷新后状态丢失问题, 补充回归验证.
+```
 
-  进行中 1 项:
-  - iunit-web: 推进导入流程重构, 已完成数据解析.
+Start each item with the label that best locates the work for a reader: the project
+name when the day spans projects, a module or feature within a single one.
 
-  汇总: 3 个项目, 2 项完成, 1 项进行中.
-```
+Keep entries compact: the file accumulates for months, so every recurring line must
+earn its place. Do not add per-day summary, total, or section-header lines; the
+numbered items already show project and count.
 
 Prefer outcomes over raw Git metrics. If no verified activity exists, say so rather
-than fabricate an entry.
+than fabricate an entry. For a range, output one entry per day with activity, oldest
+first, and skip empty days.
 
 ## Draft or record
 
@@ -76,24 +85,33 @@ write request, writes after previewing the entry. Resolve the destination in ord
 3. no destination: return the draft without writing.
 
 Read the destination before editing. Wrap each date's generated content in that date's
-own markers, `<!-- log:2026-07-31:start -->` / `<!-- log:2026-07-31:end -->`; the date
-line and every line outside the markers belong to the user. For an existing date, show
+own markers, `<!-- log:2026-07-31:start 5,a1b2c3d -->` / `<!-- log:2026-07-31:end -->`,
+where the start marker stores the day's commit count and newest commit hash across the
+scanned projects; the date line and every line outside the markers belong to the user.
+Refresh an existing block when either value changed or the user explicitly asks;
+otherwise leave it alone, because regenerated wording varies between runs. For an existing date, show
 the current block and the regenerated one before writing, then replace only that
 date's block. If the date exists without markers, append a marked block below the
-user's lines instead of editing them. Do not duplicate the date. On duplicate or
+user's lines instead of editing them. Do not duplicate the date. Insert a new date
+among the existing dated entries at its date-order position, inferring ascending or
+descending from the dates already present (ascending when that is ambiguous); content
+above or below the dated entries, such as notes or todo lists, stays where it is. On duplicate or
 unpaired markers, stop and propose the edit instead of writing. When Git shows no
 activity, leave the file unchanged and say so; the user can add a manual entry
-themselves.
+themselves. Recording a range applies these rules to each day's block independently.
 
 Scheduling is separate; set it up only when the user asks. Prefer the OS scheduler
 (Task Scheduler, cron, launchd) over agent-internal timers, which stop with the agent:
 schedule a headless run of the CLI this skill is executing in, invoking the skill with
-a recording request (in Claude Code, `claude -p "/at-daily-log record the log"`; other
-CLIs have their own headless form). Keep projects and output in config so the command
-stays stable. Before registering, confirm the schedule (suggest workdays),
-make sure the output file is resolvable, and run the exact command once; register only
-after that test run records correctly, and show how to remove the task. Headless auth
+the recording request the user asked for (in Claude Code,
+`claude -p "/at-daily-log record the log"`; other CLIs have their own headless form).
+Keep projects and output in config so the command stays stable. Before registering,
+confirm the schedule, make sure the output file is resolvable, and run the exact
+command once; register only after that test run records correctly, and show how to
+remove the task. Headless auth
 differs from the interactive session, so a failed test run means stop instead of
 registering, and show the exact command, its error output, and the likely fix (log in
-for headless use, adjust the output path). An unattended run has nobody to confirm with, so it must follow the
-marker rules exactly and skip any file it cannot edit that way.
+for headless use, adjust the output path). An unattended run has nobody to confirm
+with, so it must follow the marker rules exactly and skip any file it cannot edit that
+way: it fills missing days and refreshes days whose stored count or hash moved,
+nothing else.

package/skills/workflow/at-self-eval/SKILL.md

@@ -33,7 +33,9 @@ user can provide other author names if needed.
 
 ## Project evidence
 
-Read optional `workProjects` from `~/.agent-tools/config.jsonc`.
+Read optional `workProjects` from `~/.agent-tools/config.jsonc`. An entry is a path
+or `{ "path", "prompt" }`, where the prompt is free text this skill follows for that
+project, such as how to label items or which commits to skip.
 
 - No project named: current Git repository plus configured projects.
 - Projects named directly: only those projects.