メニュー
Review session work and optionally update agent memory. Use to capture decisions, patterns, or insights - or just to reflect without changing anything.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/NavarrePratt/claude-settings --skill rememberコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Create logically grouped, atomic git commits with well-formatted commit messages following best practices. Use this skill when you need to commit changes to a git repository with proper message formatting and atomic grouping. Before creating commits, reflect on the work just completed and surface any open questions or unresolved decisions (judgment calls made without checking, deferred edge cases, defaults picked when multiple options were viable, trade-offs that could reasonably go the other way) via AskUserQuestion so they get discussed with the user rather than silently committed.
Review code with grug-brain anti-complexity philosophy. Use when reviewing PRs, diffs, or code changes to identify unnecessary complexity.
Implement an epic's beads in a worktree with logical commits, multi-agent review, fix pipeline, and PR description generation. Use when you want to implement this epic, burn down the beads, execute the plan, or start working on an epic.
SKILL.md を表示中
SOC 職業分類に基づく
| name | remember |
| description | Review session work and optionally update agent memory. Use to capture decisions, patterns, or insights - or just to reflect without changing anything. |
The user has triggered a memory review. They may have provided context, or they may just want you to reflect on the session.
$ARGUMENTS
Your auto memory directory path is in your system prompt, in a line like:
You have a persistent auto memory directory at
~/.claude/projects/<project>/memory/.
Extract that path. If you cannot find it, use ~/.claude/projects/ and look for a subdirectory matching the current working directory.
Create the directory if it does not exist yet.
Summarize what happened this session - briefly, 2-3 sentences max.
Read your current memory index at <memory-dir>/MEMORY.md (it may not exist yet - that is fine).
Read any topic files referenced in MEMORY.md that are relevant to this session's work.
Assess whether memory needs updating. Consider:
Report your assessment. Show one of:
If no changes needed:
"Memory is current. Nothing from this session warrants an update."
Done. Stop here.
If changes are warranted: Show exactly what you would add or modify, which file it goes in, and why. Format as a diff-like preview. Then ask: "Want me to apply this?"
Wait for approval. Only write to memory files if the user confirms. If they say no or suggest edits, adjust accordingly.