learn

Store, index, and expose project learnings in learnings.jsonl.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps project learnings centralized across sessions, so teams can review, search, prune, and export knowledge instead of letting it drift.

Core Features & Use Cases

  • Centralizes learnings across sessions for quick reference and pattern discovery.
  • Supports review, search, prune, and export workflows to maintain a clean knowledge base.
  • Proactively surfaces relevant learnings when users ask about past patterns or recurring issues.

Quick Start

Use the /learn command to see recent learnings and search for specific topics.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I centralize project learnings across different sessions?

To centralize project learnings across sessions, use a dedicated storage system that reads and updates a centralized learnings store, such as a JSONL file, keeping insights organized for quick reference instead of letting them drift.

What is the best way to search past project insights and recurring issues?

The best way to search past project insights and recurring issues is to use a workflow that indexes stored learnings and proactively surfaces relevant patterns when queried about past projects.

Can I export and prune my accumulated project knowledge base?

Yes, you can export and prune your accumulated project knowledge base using supported review, search, prune, and export workflows, which help maintain a clean and relevant knowledge store.

How do I organize project learnings to surface patterns during reviews?

You organize project learnings to surface patterns by storing and indexing insights in a centralized file, allowing the system to expose relevant historical context when asked about recurring issues.

Does organizing project knowledge require any specific dependencies?

Organizing project knowledge using this specific workflow does not require any external dependencies, as it operates independently to read and update the centralized learnings store.

When should I prune my centralized learnings store?

You should prune your centralized learnings store when outdated insights accumulate, utilizing the review and prune workflows to remove irrelevant entries and maintain a clean, efficient knowledge base.