菜单
Turn Daniel's rough notes (text, voice, URL, repo path, or unresolved Q&A) into a note in notes/, stamped with the date and Claude Code version. Edits are light — these are rough cliff notes, not polished docs. Use when Daniel says "add a note", "new note", or drops rough material for this repo.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-Code-Notes --skill add-note命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Capture a Q&A exchange as a note. Daniel asks a Claude Code question, you answer, then this skill writes the question + answer into notes/ with the standard date + CC version stamp and updates the README index. Use when Daniel says "make this a note", "Q&A note", or asks a question and wants the answer filed.
Commit and push the current state of the Claude-Code-Notes repo — use after Daniel approves a drafted note (or batch of notes) and says "publish", "ship it", "push", or similar. Follows Daniel's git rule — commit everything, push immediately.
基于 SOC 职业分类
正在显示 SKILL.md
| name | add-note |
| description | Turn Daniel's rough notes (text, voice, URL, repo path, or unresolved Q&A) into a note in notes/, stamped with the date and Claude Code version. Edits are light — these are rough cliff notes, not polished docs. Use when Daniel says "add a note", "new note", or drops rough material for this repo. |
Daniel drops rough material; you file it in notes/ with a date + CC version stamp and update the README index. Claude Code changes fast, so every note records the CC version at write-time.
Edit lightly. These notes are supposed to feel rough — first-person, opinionated, sometimes unresolved. Your job is typo fixes, obvious grammar, and structure (headings if missing). Do NOT rewrite Daniel's voice, smooth out the prose, or pad it out.
Daniel's rough input may be:
Capture the stamp — run claude --version and date +%d/%m/%Y. Use these verbatim in the note frontmatter block (see template below). Do not guess the version.
Pick a filename — kebab-case, descriptive, in notes/. Check notes/ first to avoid collisions.
Write the note using this header template:
# <Title>
**Date:** DD/MM/YYYY
**Claude Code version at time of writing:** X.Y.Z
<body>
---
*Claude Code moves fast — this may be outdated by the time you read it.*
Two common body shapes:
Prose / pattern note — lede paragraph, then sections as needed, concrete examples, links.
Unresolved Q&A note — Daniel often drops these: a Source link, then Question: framing, then Question 1 / Answer 1 / ... blocks, often ending with "Issue: unresolved". Keep this structure as-is. Do not flatten it into prose. If Daniel asked you to push back or add a resolved answer, append it as a clearly labelled section at the bottom (e.g. ## Postscript — resolved answer) rather than editing his Q&A body.
Style rules:
Update README.md — add a row to the appropriate Notes Index table (or create a new section if none fits). Format:
| [Title](notes/filename.md) | DD/MM/YYYY | One-line summary |
Show Daniel the draft before doing anything else. Do NOT commit or push — that's the publish-note skill's job.
$ARGUMENTS