# Weekly Work Notion

> Summarize the current week's work from git commits and Codex conversation context, then update the configured Notion tasks database only after user confirmation.

- Skill: `louischen1905/weekly-work-notion` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add louischen1905/weekly-work-notion`
- Raw SKILL.md: https://api.skillmd.com/api/skills/louischen1905/weekly-work-notion/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: LouisChen1905 (https://skillmd.com/u/louischen1905)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/louischen1905/weekly-work-notion

---


# Weekly Work Notion

Use this skill when the user asks to summarize this week's work and record it in Notion tasks.

## Purpose

Prepare a concise weekly work summary from local development evidence, confirm the summary with the user, then update the user's Notion tasks database without creating duplicate or near-duplicate tasks.

Default Notion tasks target:

`https://app.notion.com/p/e209332e232382698fc481b31a7775f1?v=7bd9332e23238375b09888ee58697b18&source=copy_link`

Default git author filter:

`175912@cn.chervongroup.com`

## Evidence To Gather

- Use the current date and local timezone to determine the current week unless the user specifies a date range.
- Inspect git history for commits authored by `175912@cn.chervongroup.com` in that week. Prefer commands such as `git log --author=175912@cn.chervongroup.com --since=<start> --until=<end> --stat --oneline` and inspect full commit messages or changed files when the summary needs more detail.
- Include relevant Codex conversation history available in the current thread, summaries, local artifacts, or explicit user-provided context. Do not invent unavailable conversation history; state any gap briefly in the draft summary.
- Keep unrelated authors' commits out of the core summary unless they are needed to explain collaborative work.

## Draft For Confirmation

Before writing to Notion, present the proposed weekly work content to the user and ask for confirmation. The draft should normally include:

- Week range.
- Key completed work.
- Important fixes or investigations.
- Open follow-ups or risks, if visible from the evidence.
- Source basis, such as commit count and whether Codex conversation context was available.

Do not create or update Notion pages until the user explicitly confirms the content or provides edits to apply.

## Updating Notion

Use the Notion connector or available Notion tools when they are available. If Notion tools are not currently callable, discover them through tool search before saying the update cannot be performed.

Before creating a task:

- Search the target Notion tasks database/page for the same week range and for semantically related weekly-summary tasks.
- Treat tasks as related when they have the same week, substantially overlapping title, or clearly cover the same work stream.
- Prefer updating an existing matching or related task over creating a new one.
- If multiple plausible existing tasks match, show the candidates and ask the user which one to update.

When updating or creating:

- Preserve existing useful task content and append or merge the new weekly summary instead of overwriting unrelated information.
- Include the confirmed week range and enough detail for later review.
- Record that the summary was prepared from git commits by `175912@cn.chervongroup.com` and available Codex conversation context.
- Stop after one successful Notion mutation unless the user explicitly asks for more.

## Safety Boundary

The user's confirmation of the summary authorizes only the specific Notion update described in that confirmation. If the final Notion target, matched task, or written content changes materially after confirmation, ask again before mutating Notion.