daily-report-automation

name	daily-report-automation
description	Create, inspect, or update a scheduled automation that drafts high-quality Chinese daily work reports from recent agent conversations and same-day Git commit evidence.

Daily Report Automation

Core Idea

Use the agent runtime's built-in automation capability instead of a separate reporting CLI when available. The scheduled task should inspect accessible work conversations updated on the report date, supplement them with same-day Git commit evidence from relevant local repositories when available, synthesize a short human-reviewable Markdown daily report, and save it to a user-approved local folder.

Do not recreate a separate reporting CLI. Prefer one lightweight skill plus the report template in references/daily-report-template.md.

Default Output Location

Choose a local output directory for generated daily report Markdown files. Recommended examples:

~/DailyReports
~/Desktop/日报
<YOUR_REPORT_DIR>

Use the filename pattern {DATE_LOCAL}.report.md, for example:

<YOUR_REPORT_DIR>/2026-06-28.report.md

When a user asks for a daily report and does not provide another path, ask for or infer a reasonable local output directory. When creating or updating the scheduled report automation, keep the chosen directory as {OUTPUT_DIR}.

The recommended standing schedule is daily at 12:00 in the user's local timezone. The user can change this time when creating or updating the automation. Its job is to generate the current local date's report in {OUTPUT_DIR}. Before writing, check whether {DATE_LOCAL}.report.md already exists; if it does, do not create a duplicate report.

Create Or Update The Automation

When asked to create, view, update, or delete the scheduled report task, first discover the automation tool:

Search for automation_update, then call it according to its schema.

If the automation tool is unavailable, explain that the skill can provide the task prompt but cannot register the schedule in the current environment.

Before creating a schedule, collect or infer:

• Report time and timezone. Default to every day at 12:00 in the user's local timezone, unless the user chooses another time.
• Output directory. Default to the user's chosen {OUTPUT_DIR}.
• Date range. Default to "today"; weekly variants may summarize Monday through Sunday.
• Whether the report may include source thread ids. Default to include only compact thread references when useful.

Automation Prompt

Use this prompt body, adapting paths and schedule details:

Use $daily-report-automation to generate today's Codex daily work report.

Scope:
- Summarize all accessible Codex work threads updated on {DATE_LOCAL}, not only the current thread.
- Supplement Codex thread evidence with Git commits authored on {DATE_LOCAL} from relevant local repositories when available. Use commits only as factual reinforcement; do not let terse or noisy commit messages dominate the report.
- Focus on actual work performed, decisions made, validation results, blockers, and next steps.
- Prefer final user-visible Codex answers and task outcomes over intermediate tool noise.
- Prefer concrete Git evidence such as repository name, branch, commit count, and concise commit subjects when it clarifies what was actually changed.
- Do not include secrets, tokens, private keys, raw logs, or long command output.
- Do not invent completed work. If evidence is weak, mark confidence as medium/low and say what needs manual review.
- Keep the report concise: target 500-800 Chinese characters unless the user asks for detail.

Output:
- Write one Markdown file to {OUTPUT_DIR}\{DATE_LOCAL}.report.md.
- Use the concise global template from references/daily-report-template.md.
- Leave the "明日动作" section blank for the user to fill in; do not predict the user's tomorrow plan.
- End with a source note in this exact shape: `来源：Codex 线程 N 个；Git repo M 个；commit K 条；生成时间 12:00。`
- If no useful work is found, still create a short report saying no reportable Codex work was found.

For weekly automation, change the scope and file name:

Summarize Codex work conversations from {WEEK_START} to {WEEK_END}.
Write {OUTPUT_DIR}\{WEEK_START}_{WEEK_END}.weekly-report.md.

Report Workflow

1. Read references/daily-report-template.md before drafting the report.
2. Use built-in Codex thread tools when available:
   • list_threads to identify threads updated on the report date across local/remote hosts.
   • read_thread to read recent turn summaries for each relevant thread.
3. Supplement with same-day Git commit evidence when local repositories can be discovered safely:
   • Count repositories with commits on the report date.
   • Count same-day commits and capture concise commit subjects.
   • Use repository and branch names to improve workstream grouping.
   • Ignore merge commits and avoid raw diffs, long logs, secrets, or noisy generated-file details.
4. If thread tools are unavailable, inspect local Codex session history only when the user has approved that data source.
5. Group work by project/workstream and merge related turns. Avoid chronological chat logs.
6. Write a short manager-style report: status conclusion, top outcomes, per-workstream progress, active risks, user-filled tomorrow actions, and source note.
7. Save Markdown to the configured output directory. Create the directory if needed.

Quality Bar

The report should read like a short end-of-day status note, not like a transcript summary or audit log.

Apply these writing standards:

• Start with project/workday health so the reader immediately sees whether work is on track, at risk, or needs confirmation.
• Group related activity into outcomes by project/workstream; do not narrate thread order.
• Use Git commits as a factual cross-check for code changes, but keep the prose focused on user-visible outcomes and workstream progress.
• Keep risks actionable: name the impact and the likely mitigation or decision needed.
• Leave tomorrow actions blank for the user to fill in. Do not infer or invent the user's next-day plan.
• Always include a final source note: 来源：Codex 线程 N 个；Git repo M 个；commit K 条；生成时间 12:00。

Prefer:

• "完成 Codex 日报自动化方案取舍，决定用 Skill + automation 替代 Python CLI。"
• "推进 post-service 第 14 课 Feed 冷启动链路，讲清 ZSet、游标分页和写链路接入。"
• "重构博客分类页为根分类卡片 + 子分类列表，页面信息密度和层级表达更清晰。"

Avoid:

• "用户说确认删除。助手删除了仓库。"
• "讨论了日报。"
• "做了一些修改。"
• "继续下一步。"

Status guidance:

• Use 完成/验证 only when the final answer or evidence says work was done, verified, pushed, deleted, generated, or otherwise completed.
• Use 推进中 when work was designed, discussed, or partially implemented without final closure.
• Use 排障/待确认 only for unresolved failures. Do not mark a completed item as blocked merely because it mentions old, existing, unrelated, or already-fixed errors.
• Use 学习/分析 for explanation, research, and decision support that did not change files or external state.

Safety

• This skill is only allowed to generate daily or weekly report Markdown files.
• The only allowed write operations are creating the configured output directory when needed and writing the report file under {OUTPUT_DIR}.
• Never delete files, commit code, push to GitHub, change hooks, edit project source files, install dependencies, run deployment commands, or send external notifications from this skill, even if the user asks for those actions while invoking the report workflow.
• If the user asks for any non-report side effect, explain that it is outside this skill's scope and keep the report generation workflow separate.
• Store reports outside repositories by default so generated Markdown is not accidentally committed.
• Do not include local databases, raw transcript dumps, .codex config, hook files, token counts, or private journal/runtime files in the report unless the user explicitly asks.
• If the automation needs to inspect local Codex session files, use read-only access and summarize only the minimal evidence needed for the report.