Recall Reasoning Skill for Claude

by parcadei

Search past reasoning for relevant decisions and approaches

758 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3880

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/parcadei/Continuous-Claude-v3 --skill recall-reasoning

The instruction itself

10 sections, as written by the author

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 work
build_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 --all to index existing handoffs
Create handoffs with post-mortem sections for future recall

Reasoning files empty:

Use /commit after builds to capture reasoning
Check if .git/claude/ directory exists

Other skills for the same job

different authors, same section of the catalogue

Doc Coauthoring

by anthropics

vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens

Domain Name Brainstormer

by frostant

×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts

Scientific Brainstorming

by christophacham

×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens

GitHub Project Management

by ComeOnOliver

×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take parcadei/recall-reasoning from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.