learn

Consolidate and query project learnings across sessions using a local JSONL store.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/huichen/gstack --skill learn-huichen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/huichen/gstack/tree/main/learn
Command: npx skills add https://github.com/huichen/gstack --skill learn-huichen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage and retrieve project learnings across sessions so you don’t forget what happened and why.

Core Features & Use Cases

  • Centralized learnings store per project
  • Fast search across learnings by keywords
  • Prune stale or conflicting entries
  • Export learnings to documentation or CLAUDE.md

Quick Start

Run /learn to show the most recent learnings.

Frequently Asked Questions about learn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture and query project learnings across sessions?

To capture and query project learnings across sessions, use a local JSONL store with a per-project index to consolidate insights, search by keywords, and prevent repeating mistakes.

What is the best way to search past learnings by keyword?

The best way to search past learnings by keyword is using a centralized learnings store that supports fast search across sessions to retrieve relevant project insights.

Can I export project learnings to documentation or CLAUDE.md?

Yes, you can export project learnings to documentation or CLAUDE.md. The system supports exporting insights directly from the local JSONL store to your project files.

How do I prune stale or conflicting learnings entries?

You can prune stale or conflicting learnings entries by running commands that review patterns and remove outdated insights from the per-project index to maintain accuracy.

Does this approach work for managing insights across multiple projects?

Yes, this approach works for managing insights across multiple projects. It uses a per-project index backed by a local JSONL store to consolidate and export learnings independently.

Why do I need a local JSONL store for session learnings?

You need a local JSONL store for session learnings to maintain a persistent, centralized record of project insights that prevents forgetting what happened and why across sessions.