project-daily-summary
Skill9 starsChanged 8 months agoMITView on GitHub
Use when the user wants a same-day Codex work summary grouped by project folder or repository, combining today's Codex sessions, extracted plans, completed items, commits, and uncommitted changes, or says 项目日报, 日报, 今日工作总结, 按项目总结今天, 总结今天所有 Codex 会话, 总结今天会话+提交+未提交改动.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- borgesme/fastapi-general-templateword for word, first seen Apr 9, 2026
Other versions1 project uses a version of this.
Word for word · 1
- borgesme/fastapi-general-template★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
35 rules. About 0 are common, 26 are distinctive, and 9 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈26
Distinctive · estimate
This author's own choices. Worth a look.
9
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Do not produce a chronological 流水账.
- Distinctive: line 13
Do not summarize reasoning noise.
- Distinctive: line 14
Always summarize by project and then by major workstream.
- Very specific: line 31
Do not assume each project stores its own sessions under <project>/.codex/sessions/.
- Very specific: line 37
if git root cannot be resolved, fall back to cwd
- Distinctive: line 53
Use the local machine date, not UTC.
- Distinctive: line 61
If the directory does not exist, report that no Codex sessions were found for today and stop.
- Very specific: line 89
If that fails, use cwd as the project key.
- Distinctive: line 101
If a same-day parent session exists, merge the subagent into the parent workstream.
- Distinctive: line 102
If the parent session is missing, keep the subagent as orphan evidence and merge it into the nearest matching project workstream instead of …
- Very specific: line 108
Prefer the first meaningful user_message.
- Very specific: line 114
Prefer the last update_plan call in the session.
- Distinctive: line 122
Keep only high-level plan items.
- Very specific: line 126
Prefer the final agent_message where:
- Distinctive: line 130
If present, extract sections such as:
- Distinctive: line 141
If no final answer exists, fall back to:
- Distinctive: line 192
Use this to produce:
- Distinctive: line 197
Do not claim commits came from Codex unless the session evidence supports that inference.
- Very specific: line 201
If <project>/.specstory/history/ exists, use it only as a supplementary source.
- Distinctive: line 203
Do not let SpecStory override Codex transcript evidence when they conflict.
- Very specific: line 207
If the user also wants a same-day all-repo closeout appendix in addition to the daily summary, you may optionally invoke worktree-closeout.
- Distinctive: line 209
Use it only as an additive supplement:
- Distinctive: line 213
use this only for same-day all-repo closeout appendix scenarios
- Very specific: line 214
if the user wants a standalone closeout scan, or a repo-scoped closeout scan, use worktree-closeout directly instead of this skill
- Distinctive: line 215
if the user did not ask for the appendix, skip this step
- Distinctive: line 217
When used, append the result as one extra appendix, for example:
- Distinctive: line 226
Do not replace the main daily summary structure with the closeout appendix.
- Distinctive: line 273
Do not repeat subagent outputs separately if already merged.
- Distinctive: line 274
If evidence is missing, say so explicitly.
- Distinctive: line 275
If a project has no git repository, say that commit and uncommitted sections are unavailable.
- Distinctive: line 282
Use this policy instead:
- Distinctive: line 284
If the current project's AGENTS.md defines a daily-summary output directory, follow it.
- Distinctive: line 286
Use a configurable filename pattern such as:
- Distinctive: line 292
If the user does not explicitly override the path or filename, use this location and naming convention automatically.
- Distinctive: line 294
If the user explicitly says not to save the report, skip file creation and return the summary in chat only.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
project-daily-summary
Summarize today's Codex work by project. Use global Codex session transcripts as the primary evidence source, then enrich with git commits and uncommitted changes. Prioritize plans and final outcomes over process chatter.
Core Rule
Do not produce a chronological 流水账. Do not summarize reasoning noise. Always summarize by project and then by major workstream.
Source Priority
~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl~/.codex/history.jsonl<project>/.specstory/history/if it existsgit log,git status --short,git diff --stat
Important Environment Assumption
In this Codex environment, session transcripts are primarily stored under:
~/.codex/sessions/YYYY/MM/DD/Do not assume each project stores its own sessions under <project>/.codex/sessions/.
Map sessions back to projects using:
session_meta.payload.cwd- then normalize with
git -C <cwd> rev-parse --show-toplevel - if git root cannot be resolved, fall back to
cwd
Scope
Default scope
Summarize all projects that appear in today's Codex sessions.
If the user provides folders
Summarize only those folders or repositories.
Workflow
Step 1: Determine today's local date
Use the local machine date, not UTC.
Build the session directory path:
~/.codex/sessions/YYYY/MM/DD/If the directory does not exist, report that no Codex sessions were found for today and stop.
Step 2: Load today's session transcripts
Read all:
rollout-*.jsonlFor each session, extract from the first session_meta line:
- session id
- cwd
- branch
- commit hash
- repository url
- whether it is a subagent session
- parent thread id if present
Step 3: Group by project
For each session:
- Try:
git -C <cwd> rev-parse --show-toplevel - If that fails, use
cwdas the project key.
Output one section per project, not one section per raw session.
Step 4: Handle subagents correctly
Many sessions may be spawned subagents. Do not list each child session as a separate user-facing item.
Use this policy:
- Main sessions are the primary narrative units.
- Subagent sessions are supporting evidence only.
- If a same-day parent session exists, merge the subagent into the parent workstream.
- If the parent session is missing, keep the subagent as orphan evidence and merge it into the nearest matching project workstream instead of listing it standalone.
Step 5: Extract structured signals from each session
Goal
Prefer the first meaningful user_message.
Rewrite it into one short Chinese objective sentence.
Plan
Prefer the last update_plan call in the session.
Summarize it into:
- 已完成
- 进行中
- 待处理
Keep only high-level plan items.
Completion
Prefer the final agent_message where:
phase == final_answer
If present, extract sections such as:
STATUSCHANGED_FILESTESTS_RUNNOTES
Convert them into concise outcome statements.
Fallback when no final answer exists
If no final answer exists, fall back to:
- latest plan state
- changed files if detectable
- git evidence
- latest meaningful assistant message
Step 6: Ignore process noise
Ignore by default:
- reasoning items
- token counts
- most system and developer prompt content
- most intermediate tool chatter
- repeated subagent scaffolding
Keep only:
- user goal
- extracted plan
- final outcome
- changed files
- tests run
- risks or blockers
Step 7: Merge sessions into major workstreams
Within each project, merge multiple sessions into a few major workstreams.
Use these signals:
- same branch or worktree
- same or similar user goal
- overlapping changed files
- same plan file
- same parent thread chain
- same feature, bug, review, or skill topic
Target 1 to 5 workstreams per project, not dozens of tiny entries.
Step 8: Add git evidence
For each project, run:
git -C <repo> log --since="YYYY-MM-DD 00:00" --until="YYYY-MM-DD 23:59" --pretty=format:"%h %s"
git -C <repo> status --short
git -C <repo> diff --statUse this to produce:
- 今日 commits
- 当前未提交改动
Do not claim commits came from Codex unless the session evidence supports that inference.
Step 9: Optional SpecStory supplementation
If <project>/.specstory/history/ exists, use it only as a supplementary source.
Do not let SpecStory override Codex transcript evidence when they conflict.
Step 10: Optional closeout appendix
If the user also wants a same-day all-repo closeout appendix in addition to the daily summary, you may optionally invoke worktree-closeout.
Use it only as an additive supplement:
project-daily-summaryremains the primary same-day, by-project reportworktree-closeoutis optional and only for the appendix view- use this only for same-day all-repo closeout appendix scenarios
- if the user wants a standalone closeout scan, or a repo-scoped closeout scan, use
worktree-closeoutdirectly instead of this skill - if the user did not ask for the appendix, skip this step
When used, append the result as one extra appendix, for example:
## 附录:Closeout / 未收口 Worktree / 分支收口状态
- 扫描范围:当天所有 repos
- 需优先收口的 repo / branch / worktree:
- 建议后续动作 / artifact 路径:Do not replace the main daily summary structure with the closeout appendix.
Output Format
# Codex Project Daily Summary
日期:YYYY-MM-DD
## 总览
- 项目数:
- 会话数:
- 主要推进:
- 今日仍未收尾:
## 项目:<repo-or-folder>
- 分支 / 仓库:
- 今日 Codex 目标:
- 今日计划提炼:
- 今日完成事项:
- 今日 commits:
- 当前未提交改动:
- 风险 / 未完成项:
- 建议下一步:
## 项目:<repo-or-folder>
...
## 跨项目总结
- 今天最重要的推进
- 重复出现的问题
- 明天最值得先做的 1-3 件事
## 附录:Closeout / 未收口 Worktree / 分支收口状态(可选)
- 仅当用户额外要求当天所有 repo 的 closeout / worktree / 分支收口状态时添加
- 可附 `worktree-closeout` 的摘要、优先级、artifact 路径Writing Rules
- Write in Chinese.
- Group by project first.
- Lead with results, not process.
- Distinguish clearly between:
- 会话计划
- 已完成事项
- 已提交内容
- 未提交改动
- Do not repeat subagent outputs separately if already merged.
- If evidence is missing, say so explicitly.
- If a project has no git repository, say that commit and uncommitted sections are unavailable.
Default Save Location
For public distribution, do not hardcode a personal sync folder.
Use this policy instead:
- If the current project's
AGENTS.mddefines a daily-summary output directory, follow it. - Otherwise, ask the user for the output directory the first time.
- Use a configurable filename pattern such as:
YYYY-MM-DD-project-daily.mdIf the user does not explicitly override the path or filename, use this location and naming convention automatically.
If the user explicitly says not to save the report, skip file creation and return the summary in chat only.
Trigger Phrases
- 项目日报
- 日报
- 今日工作总结
- 按项目总结今天
- 总结今天所有 Codex 会话
- 总结今天会话+提交+未提交改动
- codex project daily summary
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

