recall-reasoning
Search past reasoning for relevant decisions and approaches
pinned to #d07ff4bupdated last month
Ask your AI client: “install skills/recall-reasoning”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/recall-reasoningmetahub onboarded this repo on the author's behalf.
If you own github.com/parcadei/Continuous-Claude-v3 on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
3,883
Last commit
last month
Latest release
published
- #agents
- #claude-code
- #claude-code-cli
- #claude-code-hooks
- #claude-code-mcp
- #claude-code-skills
- #claude-code-subagents
- #claude-skills
- #mcp
About this skill
Pulled from SKILL.md at publish time.
Search through previous sessions to find relevant decisions, approaches that worked, and approaches that failed. Queries two sources:
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.d07ff4b· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
7 passed2 warningsDescription qualitywarn
8 words · 59 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
Homepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
README is present and substantial
45,577 chars · 22 sections · 38 code blocks
Tags / topics declared
9 total — agents, claude-code, claude-code-cli, claude-code-hooks, claude-code-mcp, claude-code-skills (+3)
README has usage / example sections
found: Quick Start · Installation · Installation (+1)
Homepage / docs URL declared
no homepage declared (registry will use the repo URL) — info-only, not blocking
Description is substantive
Description is 8 words.
Documentation present and substantive
Documentation present (SKILL.md, 406 words).
Documentation shows usage
Documentation includes 3 code examples.
Release history
1- releasecurrentd07ff4bwarnlast month
Contents
Recall Past Work
Search through previous sessions to find relevant decisions, approaches that worked, and approaches that failed. Queries two sources:
- Artifact Index - Handoffs, plans, ledgers with post-mortems (what worked/failed)
- Reasoning Files - Build attempts, test failures, commit context
When to Use
- Starting work similar to past sessions
- "What did we do last time with X?"
- Looking for patterns that worked before
- Investigating why something was done a certain way
- Debugging an issue encountered previously
Usage
Primary: Artifact Index (rich context)
uv run python scripts/core/artifact_query.py "<query>" [--outcome SUCCEEDED|FAILED] [--limit N]
This searches handoffs with post-mortems (what worked, what failed, key decisions).
Secondary: Reasoning Files (build attempts)
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/search-reasoning.sh" "<query>"
This searches .git/claude/commits/*/reasoning.md for build failures and fixes.
Examples
# Search for authentication-related work
uv run python scripts/core/artifact_query.py "authentication OAuth JWT"
# Find only successful approaches
uv run python scripts/core/artifact_query.py "implement agent" --outcome SUCCEEDED
# Find what failed (to avoid repeating mistakes)
uv run python scripts/core/artifact_query.py "hook implementation" --outcome FAILED
# Search build/test reasoning
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/search-reasoning.sh" "TypeError"
What Gets Searched
Artifact Index (handoffs, plans, ledgers):
- Task summaries and status
- What worked - Successful approaches
- What failed - Dead ends and why
- Key decisions - Choices with rationale
- Goal and constraints from ledgers
Reasoning Files (.git/claude/):
- Failed build attempts and error output
- Successful builds after failures
- Commit context and branch info
Interpreting Results
From Artifact Index:
✓= SUCCEEDED outcome (pattern to follow)✗= FAILED outcome (pattern to avoid)?= UNKNOWN outcome (not yet marked)- Post-mortem sections show distilled learnings
From Reasoning:
build_fail= approach that didn't workbuild_pass= what finally succeeded- Multiple failures before success = non-trivial problem
Process
- Run Artifact Index query first - richer context, post-mortems
- Review relevant handoffs - check what worked/failed sections
- If needed, search reasoning - for specific build errors
- Apply learnings - follow successful patterns, avoid failed ones
No Results?
Artifact Index empty:
- Run
uv run python scripts/core/artifact_index.py --allto index existing handoffs - Create handoffs with post-mortem sections for future recall
Reasoning files empty:
- Use
/commitafter builds to capture reasoning - Check if
.git/claude/directory exists
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/recall-reasoning