notion

Generates daily development reports from git commits and plan documents for Notion upload.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/nayounghye/my-claude-skills --skill notion-nayounghye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: notion
Source: https://github.com/nayounghye/my-claude-skills/tree/main/notion
Command: npx skills add https://github.com/nayounghye/my-claude-skills --skill notion-nayounghye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing detailed daily development reports is tedious, and engineers often forget why decisions were made. This Skill automates the creation of decision-focused daily reports by mining git history and plan markdown files, then publishing them to a Notion database. ## Core Features & Use Cases - Automated Data Collection: Gathers commits and newly added Q&A sections from plan markdown files for a given date or date range using git log and diff. - Decision-Record Reports: Transforms Q&A background, alternatives, and rationale into structured STAR-format sections with depth checks (file paths, metrics, rejected alternatives, trade-offs). - Notion Integration: Reads the database's template page as the format source of truth, prevents duplicate pages via update mode, and resolves the target database per project without hardcoded IDs. - Use Case: After a day of implementation work, run the command to produce a Notion daily report that captures not just what changed but why, including rejected design alternatives and measured improvements. ## Quick Start Run /notion with no arguments to generate today's development report from recent commits and plan documents, or pass a date like /notion 2026-05-12 for a specific day.

Frequently Asked Questions about notion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a daily development report from git commits?▼

Run the command with no arguments to use today's date, or pass a specific date or date range. It collects commits with git log, identifies changed plan markdown files, reads newly added Q&A sections, and writes a structured report.

How does the report get uploaded to a Notion database?▼

It uses Notion MCP tools to search for the target database, read the template page for the section structure, check for an existing page with the same date, and either update that page's blocks or create a new page.

Can I use this with a different Notion database per project?▼

Yes. The database is resolved per project: an explicit user instruction, a .claude/notion-db.json config file, or automatic search by project name. If multiple candidates exist, it asks the user rather than guessing.

What happens if I run the report command twice for the same date?▼

It prevents duplicates by searching for an existing page with the same date title in the target database. If found, it deletes the old blocks and writes the new content into that page instead of creating another one.

Why does the report reject shallow one-line summaries?▼

The skill enforces a depth check requiring concrete file paths, function names, metrics, rejected alternatives, and trade-offs per section. If the draft falls short, it re-reads the source Q&A sections and expands the content before uploading.