Prompts · PromptDocs & LearningReviewed

learn-eval

Extract reusable patterns from the session, self-evaluate quality before saving, and determine the right save location (Global vs Project).

View on GitHub

Kind: Prompt
Works with: Claude Code, Codex
Source: affaan-m/ECC @ d3b8a3e90890
Path: commands/learn-eval.md
License: MIT
Jobs: Review

InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.

# /learn-eval - Extract, Evaluate, then Save

Extends `/learn` with a quality gate, save-location decision, and knowledge-placement awareness before writing any skill file.

## What to Extract

Look for:

1. **Error Resolution Patterns** — root cause + fix + reusability
2. **Debugging Techniques** — non-obvious steps, tool combinations
3. **Workarounds** — library quirks, API limitations, version-specific fixes
4. **Project-Specific Patterns** — conventions, architecture decisions, integration patterns

## Process

1. Review the session for extractable patterns
2. Identify the most valuable/reusable insight

3. **Determine save location:**
   - Ask: "Would this pattern be useful in a different project?"
   - **Global** (`~/.claude/skills/<pattern-name>/SKILL.md`): Generic patterns usable across 2+ projects (bash compatibility, LLM API behavior, debugging techniques, etc.)
   - **Project** (`.claude/skills/<pattern-name>/SKILL.md` in current project): Project-specific knowledge (quirks of a particular config file, project-specific architecture decisions, etc.)
   - When in doubt, ask; never default uncertain content to Global persistence.
…