Session Logging

Database Schema — ALL Properties MUST Be Filled

Tags Options

Choose from: Notion AI, Replit, Automation, Architecture, Workflow, Agent, MCP, Prompt Engineering, Group Digest, AI First Mover Group

Execution Flow

Step 0: Calculate Session Duration

START=$(cat ~/.claude/.session_start 2>/dev/null)
NOW=$(date -u +%Y-%m-%dT%H:%M:%SZ)

If ~/.claude/.session_start exists, calculate hours:

python3 -c "
from datetime import datetime
start = datetime.fromisoformat('$START'.replace('Z','+00:00'))
end = datetime.fromisoformat('$NOW'.replace('Z','+00:00'))
hrs = round((end - start).total_seconds() / 3600, 1)
print(f'Duration: {hrs} hours')
"

Step 1: Read Config

Read ~/.claude/skills/notion-config.md to get:

• NOTION_USER_ID — for the Person property
• NOTION_TOKEN — shared Atomic AI token
• Verify both exist. If missing, STOP and tell user.

Step 2: Analyze the Conversation

Review everything done in this session:

• What features were built/fixed?
• What bugs were solved?
• What was deployed?
• What decisions were made?
• What's still pending?

Step 3: Find Project and Task (MANDATORY — Do NOT Skip)

Project — MUST find one:

curl -s -X POST 'https://api.notion.com/v1/databases/f3f435b9-e9ab-4665-9e96-54f104a049f0/query' \
  -H 'Authorization: Bearer NOTION_TOKEN' \
  -H 'Content-Type: application/json' -H 'Notion-Version: 2022-06-28' \
  -d '{"page_size": 30}'

• Search through results for a matching project name
• If no match found → ASK the user: "This session belongs to which project?"
• NEVER leave Project empty

Task — Search and link if exists:

curl -s -X POST 'https://api.notion.com/v1/databases/cdf0fa82-6bf4-4163-8b16-0e5a52307ff8/query' \
  -H 'Authorization: Bearer NOTION_TOKEN' \
  -H 'Content-Type: application/json' -H 'Notion-Version: 2022-06-28' \
  -d '{"page_size": 20, "sorts": [{"timestamp": "last_edited_time", "direction": "descending"}]}'

• If matching task found → link it
• If no matching task → OK to leave empty, but state "No matching task found"

Step 4: Check for Existing Page (Avoid Duplicates)

curl -s -X POST 'https://api.notion.com/v1/databases/464f84cb-950c-456c-875a-e55530bef9a8/query' \
  -H 'Authorization: Bearer NOTION_TOKEN' \
  -H 'Content-Type: application/json' -H 'Notion-Version: 2022-06-28' \
  -d '{"page_size": 5, "sorts": [{"timestamp": "created_time", "direction": "descending"}]}'

If today's page exists for this user → update it. If not → create new.

Step 5: Create the Session Log Page

Properties — ALL must be set:

{
  "Session Name": { "title": [{ "text": { "content": "Descriptive session title" } }] },
  "Summary": { "rich_text": [{ "text": { "content": "One sentence summary" } }] },
  "Person": { "people": [{ "id": "YOUR_NOTION_USER_ID" }] },
  "Contributor": { "select": { "name": "🦐 Claude Code" } },
  "Source": { "select": { "name": "Claude Code" } },
  "Tags": { "multi_select": [{ "name": "Tag1" }, { "name": "Tag2" }] },
  "Lesson Learned": { "rich_text": [{ "text": { "content": "What was learned" } }] },
  "Duration (hrs)": { "number": 1.5 },
  "Project": { "relation": [{ "id": "PROJECT_PAGE_ID" }] },
  "Task": { "relation": [{ "id": "TASK_PAGE_ID" }] }
}

Content body — use Decision-Focused format (NOT changelog):

Session Log is NOT a changelog! Don't just list actions (did A, did B). Write a decision log + context.

Title format: Session: YYYY-MM-DD - [Short Topic]

Summary property: Only put 3-5 index sentences (so AI search can efficiently hit keywords). Full content goes in page body.

Page body — each major topic must include these sections:

## [Topic Number]. [Topic Name] — [One-sentence description]

### Discussion Process
What options were considered? What context led to this discussion?

### Decision
Which approach was chosen? Why?

### Rejected Alternatives
- ❌ [Option A] — [Why not chosen]
- ❌ [Option B] — [Why not chosen]
(Prevents repeating the same mistakes in the future)

### Standards Established
What new rules/conventions were created?

### Execution
What was actually done (brief)

### Pitfalls Encountered
What was done wrong and reverted? What approaches failed?

Must include at the end:

## New Skills / Standards Established (For Future Reference)
| Standard | Details |
|---|---|
| [Standard Name] | [Specific Details] |

## Lesson Learned
1. [Transferable takeaway]

## Next Session TODO
- [ ] [Specific task]

Writing principles:

• Anyone with zero context reading this log in the future should understand why the system looks the way it does
• Decision + context is more valuable than action
• Rejected alternatives are as important as the chosen approach (prevents retrying the same things)
• Never write only frameworks (e.g., "Defined storage logic") — must write out the specific details

Step 6: Verify and Report

After creating/updating:

1. Confirm the page was created successfully
2. Print the Notion URL so the user can verify
3. List which properties were filled and which were left empty (there should be NONE empty except Task if no match)

Pre-Submit Checklist

Before sending the API call, verify:

• Session Name is descriptive (not generic like "Session Log")
• Summary is one sentence
• Person is set to the USER's Notion ID (NOT the bot's ID)
• Contributor is 🦐 Claude Code
• Source is Claude Code
• Tags has at least one tag
• Lesson Learned is filled (even if "Routine session")
• Duration is calculated from session start
• Project relation is linked (NEVER empty)
• Task relation is linked if a matching task exists

Trigger Words

Activate this skill when user says:

• "logout" — CRITICAL: do NOT log out of any CLI tools! Just save session log to Notion
• "/log"
• "log session" / "save session" / "end session"

Combining Multiple Logs Per Day

When updating an existing page for the same day:

• Add new activities under existing category headings if they match
• Create new headings for new categories
• Update the Summary property to cover all activities
• Do NOT duplicate existing content