learn

Capture and organize project learnings into a searchable JSONL knowledge base.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill learn-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learn
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-learn
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill learn-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Development teams repeatedly encounter the same bugs, architectural debates, and edge cases across sessions and sprints. This Skill captures those moments as structured learnings so the team builds institutional memory instead of starting from zero every time.

Core Features & Use Cases

  • Learning Management: Review, search, prune stale entries, and export what gstack has recorded across sessions.
  • Proactive Recall: Surface past patterns when the user asks "didn't we fix this before?" or wonders about historical decisions.
  • Use Case: A team debugging a flaky test can instantly surface whether the same issue appeared in a previous sprint and what the resolution was.

Quick Start

Use the learn skill to show me what we've learned about authentication bugs in this project.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I stop repeated bug recurrence across development sprints?

To stop repeated bug recurrence across development sprints, you can capture and organize project learnings into a searchable knowledge base. This builds institutional memory so your team surfaces past patterns and resolutions instead of starting from zero.

What is institutional memory in software engineering and how does a knowledge base manage it?

Institutional memory in software engineering is the retained knowledge of past bugs, architectural debates, and edge cases. A knowledge base manages it by indexing development session history into structured learnings for proactive recall and pattern recognition.

How do I search historical session history to find previous bug fixes?

You can search historical session history by querying the recorded project learnings using natural language. This proactively surfaces past resolutions and patterns when you ask if a specific issue or flaky test appeared in a previous sprint.

Do I need a specific runtime to store project learnings and track session history?

Yes, you need the gstack runtime to store project learnings and track session history. It uses JSONL learning storage to index, prune stale entries, and export historical insights across sprints and team members.

How do I prune stale entries from an institutional memory knowledge base?

You prune stale entries from an institutional memory knowledge base using the learning management features of the gstack runtime. This allows you to review, clean up, and export only the relevant historical insights recorded across sessions.