<aside> 📋 DRAFT template for the /log Claude Code skill (https://github.com/swastij/claude-log-skill). Duplicate this whole page into your own private space, then point ~/.notion-learnings.json at the three databases below. Property names must stay exactly as they are: the script addresses them by name.
</aside>
A personal knowledge base, one row per task from your tracker (ClickUp, Jira, Linear, GitHub issues; the script only needs an id): what surprised you, how the thing actually works, the decisions you made (with alternatives rejected) and the questions you asked or should have asked. The PR records what changed; this records why, and what you would do differently. Not team-facing.
printf '%s' 'ntn_...' > ~/.notion-token && chmod 600 ~/.notion-token
cat > ~/.notion-learnings.json <<'JSON'
{ "tasks": "<tasks db id>", "decisions": "<decisions db id>", "questions": "<questions db id>" }
JSON
python3 -I ~/.claude/scripts/notion-log.py --dry-run entry.json
Type /log in Claude Code when a PR is opened or a ticket reaches Done. The skill:
<aside> 🔁 Re-running is safe: the task is upserted by Task ID, and Decision / Question rows whose title already exists for that task are skipped. To change an existing row, edit it in Notion.
</aside>