Learning Summary

Learning Summary

Extracts and documents key insights, concepts, and learnings from the current conversation. Output is blog-ready with YAML frontmatter for Astro Content Collections.

Execution Algorithm

Step 1: Read Configuration

Read ~/.claude/skills/learning-summary/config.yaml:

learning_repo: "/Users/jaykim/Documents/Projects/ai-learning"
output_dir: "blog/src/content/learnings"
auto_commit: false
auto_push: false

If config not found: Use defaults (current directory, no auto-commit)

Step 2: Analyze Conversation

Review the entire conversation history to identify:

Also extract metadata for frontmatter:

Step 3: Generate Filename

Create descriptive filename based on main topic:

IMPORTANT: Run date '+%Y-%m-%d' to get the exact current date. Never estimate.

Format: YYYY-MM-DD-brief-topic-description.md

Examples:

• 2026-01-17-claude-code-marketplace-guide.md
• 2026-01-17-python-async-programming.md
• 2026-01-17-docker-compose-networking.md

Step 3.5: Check for Existing Files

After generating the filename, scan the output directory for conflicts:

Check 1 — Exact filename match:

Glob: {output_dir}/{filename}

If the exact file exists → it's the same topic on the same day.

Check 2 — Same-date files (even if topic differs):

Glob: {output_dir}/{YYYY-MM-DD}-*.md

Collect all files with today's date prefix.

If any existing files are found, ask the user:

AskUserQuestion(
  question: "오늘 날짜의 학습 파일이 이미 있습니다. 어떻게 할까요?",
  options: [
    {
      label: "이어서 추가 (Append)",
      description: "기존 파일 맨 아래에 새 섹션으로 추가합니다."
    },
    {
      label: "새 파일 생성 (New File)",
      description: "별도 파일로 독립 저장합니다. (파일명 충돌 시 -2 접미사 추가)"
    }
  ]
)

Show existing filenames in the question for context (e.g., Found: 2026-03-03-python-async.md).

If user selects Append:

• Read the existing file with the Read tool
• In Step 5, use Edit (not Write) to append a --- separator + new content block at the end
• Update the frontmatter tags to merge old + new tags (deduplicated)
• Skip frontmatter rewrite if it would break existing structure — append only to body

If user selects New File:

• If exact filename conflict → append -2 suffix (e.g., 2026-03-03-topic-2.md)
• Proceed normally with Write in Step 5

If no existing files found: Skip this step entirely, proceed to Step 4.

Step 4: Structure Document

Generate a blog-ready markdown file with YAML frontmatter:

---
title: "[Main Topic Title]"
date: YYYY-MM-DD
description: "[1-2 sentence summary of key insight]"
category: learnings
tags: ["tag1", "tag2", "tag3"]
source: "https://..."
lang: en
draft: false
---

## Key Concepts

[Key concepts with clear definitions]

## New Learnings

[New learnings with before/after]

## Practical Examples

[Code, commands, examples]

## Common Misconceptions

[Clarified misconceptions]

## References

[Files, URLs, resources]

## Next Steps

[Follow-up actions]

Important formatting rules:

• Do NOT include # Title heading in body (the blog layout renders title from frontmatter)
• Body starts with ## Key Concepts or first applicable section
• category is always learnings
• tags are lowercase, kebab-case, as a YAML array
• source is optional (omit the field entirely if no primary URL)
• description should be under 160 characters for SEO
• Empty sections should be omitted entirely

Step 5: Save Document

Save location: {learning_repo}/{output_dir}/{filename}

Example: /Users/jaykim/Documents/Projects/ai-learning/blog/src/content/learnings/2026-01-17-topic.md

Use Write tool to create the markdown file.

Step 6: Git Operations (if auto_commit)

Only if auto_commit: true in config:

cd "$learning_repo"
git add "blog/src/content/learnings/$filename"
git commit -m "Add learning: $topic

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>"

If auto_push: true, also run:

git push

When pushed to main, GitHub Actions will automatically build and deploy the blog.

Step 7: Confirm to User

Show the user:

• Full path of saved file
• Brief summary of documented content
• Git commit status (if auto_commit enabled)
• Blog URL where post will appear after deploy
• Offer to open file or make adjustments

Trigger Phrases

English:

• "summarize what I learned"
• "document my learnings"
• "create learning summary"
• "capture insights from this conversation"

Korean:

• "지금까지 대화 정리해줘"
• "배운 내용 문서화"
• "정리해서 문서로"

Quick Reference

When to Use

Use this skill when:

• End of significant learning conversation
• After understanding a complex topic
• When you want to preserve key insights
• Before switching to a different subject
• After solving a challenging problem

Skip when:

• Very short Q&A (single question/answer)
• Simple command lookup
• Already well-documented elsewhere
• Trivial clarifications

Error Handling

Configuration

Edit ~/.claude/skills/learning-summary/config.yaml:

# Dedicated AI learning repository (absolute path)
learning_repo: "/Users/jaykim/Documents/Projects/ai-learning"

# Output directory (relative to learning_repo)
# Points to blog content directory for direct blog publishing
output_dir: "blog/src/content/learnings"

# Filename pattern (will be auto-generated based on date and topic)
filename_pattern: "YYYY-MM-DD-topic.md"

# Auto-commit to git
auto_commit: false

# Auto-push to remote (requires auto_commit: true)
auto_push: false

# Default sections to include
sections:
  - key_concepts
  - new_learnings
  - practical_examples
  - misconceptions
  - references
  - next_steps

# Language preference (auto-detect or set to 'ko'/'en')
language: en

Additional Resources

See references/ directory:

• template.md - Document template with examples
• best-practices.md - Tips for writing effective learning notes
• configuration.md - Detailed configuration guide