Claude Skills by munhq

Answer code questions structurally instead of reading whole files. Use when you need to find where something is defined, read one function, see what calls a symbol, trace imports, judge what a change breaks, or orient yourself in an unfamiliar file or repository. Reach for this before Read, Grep or Glob on a code question — and equally before `grep`, `rg`, `cat`, `head`, `sed -n` or `find` in a shell, which is where the same question goes when a harness or permission mode routes file work thr...

See what changed across past AI-coding sessions with chat-recall. Use when the user asks "what did I change 2h ago", "what files did we touch", "what happened in that session", "did that session actually ship", "which sessions edited <file>", or wants diffs/commits/edit-history that isn't in the current working tree. Reconstructs edits, diffs, commits, and outcomes from indexed sessions.

Find past AI-coding work with chat-recall. Use when the user asks "remember when we…", "have we done X before", "find my notes/sessions on…", "where did we discuss Y", "what did I ask about Z", or otherwise wants to locate earlier conversations, plans, tasks, or notes across all their AI tools. Searches the unified memory (sessions, plans, tasks, CLAUDE.md, history, diaries).

Store and recall durable facts, decisions, and notes with chat-recall's knowledge graph and diary. Use when the user says "remember this", "note that we decided…", "what do you know about X", "did we decide Y", "what's our convention for Z", or when a non-obvious decision/preference is made that future sessions should know. Covers the temporal knowledge graph, decision records, the agent diary, and a scoped key/value store.

Get the state of a project from chat-recall. Use when the user asks "what's been happening in <project>", "catch me up on this repo", "what's the state of X", about time/cost/activity across a project, or about code findings and recommended fixes. Owns the ranked findings views — "what should I fix next", "what should I work on", "what should I tell Claude about this repo", "turn these findings into tasks". Also owns the shared task board and the team view — "what are my open tasks", "create ...

Resume or cold-start work using chat-recall. Use when the user says "continue", "pick up where we left off", "resume our work", "carry on with X", starts a new session on an ongoing task, or references something from "last time" that isn't in the current context. Rebuilds prior context from past sessions instead of asking the user to re-explain.

Recall past AI-coding work — prior sessions, decisions, and project history — through the chat-recall MCP tools (mcp__chat-recall__recall_*). Use when the user says "continue" / "pick up where we left off", "did we decide X", "remember when we…", "what was I doing", "what do you know about this project/me", or otherwise references earlier work that is not in the current context. Also the entry point for the surfaces no focused skill owns: leaked secrets ("did I paste an API key"), the shared ...

See what changed across past AI-coding sessions with chat-recall. Use when the user asks "what did I change 2h ago", "what files did we touch", "what happened in that session", "did that session actually ship", "which sessions edited <file>", or wants diffs/commits/edit-history that isn't in the current working tree. Reconstructs edits, diffs, commits, and outcomes from indexed sessions.

Find past AI-coding work with chat-recall. Use when the user asks "remember when we…", "have we done X before", "find my notes/sessions on…", "where did we discuss Y", "what did I ask about Z", or otherwise wants to locate earlier conversations, plans, tasks, or notes across all their AI tools. Searches the unified memory (sessions, plans, tasks, CLAUDE.md, history, diaries).

Store and recall durable facts, decisions, and notes with chat-recall's knowledge graph and diary. Use when the user says "remember this", "note that we decided…", "what do you know about X", "did we decide Y", "what's our convention for Z", or when a non-obvious decision/preference is made that future sessions should know. Covers the temporal knowledge graph, decision records, the agent diary, and a scoped key/value store.

Get the state of a project from chat-recall. Use when the user asks "what's been happening in <project>", "catch me up on this repo", "what's the state of X", about time/cost/activity across a project, or about code findings and recommended fixes. Owns the ranked findings views — "what should I fix next", "what should I work on", "what should I tell Claude about this repo", "turn these findings into tasks". Also owns the shared task board and the team view — "what are my open tasks", "create ...

Resume or cold-start work using chat-recall. Use when the user says "continue", "pick up where we left off", "resume our work", "carry on with X", starts a new session on an ongoing task, or references something from "last time" that isn't in the current context. Rebuilds prior context from past sessions instead of asking the user to re-explain.

Recall past AI-coding work — prior sessions, decisions, and project history — through the chat-recall MCP tools (mcp__chat-recall__recall_*). Use when the user says "continue" / "pick up where we left off", "did we decide X", "remember when we…", "what was I doing", "what do you know about this project/me", or otherwise references earlier work that is not in the current context. Also the entry point for the surfaces no focused skill owns: leaked secrets ("did I paste an API key"), the shared ...