learn

Track, search, and prune session-based learnings from JSONL logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of fragmented project knowledge by centralizing, searching, and pruning the lessons learned across multiple AI-assisted engineering sessions.

Core Features & Use Cases

  • Knowledge Retrieval: Search through past project learnings to avoid repeating mistakes or re-solving previously fixed issues.
  • Lifecycle Management: Prune stale information and export accumulated insights for documentation or team sharing.
  • Use Case: When you encounter a recurring bug, use this skill to query past sessions to see if a similar issue was previously diagnosed and resolved.

Quick Start

Ask the learn skill to show all project learnings from previous sessions.

Frequently Asked Questions about learn

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

FAQPage Schema
How do I track and search past project learnings from previous engineering sessions?

To track project learnings, this skill manages the lifecycle of session-based knowledge by logging insights to project-specific JSONL files. You can search these historical logs within the gstack ecosystem to retrieve past resolutions and avoid re-solving fixed issues.

How do I manage and prune stale knowledge from my project documentation?

You can manage accumulated insights by pruning stale information and exporting the remaining knowledge for documentation. This lifecycle management ensures your project knowledge base remains relevant and accurate for team sharing.

Does this knowledge management approach require specific local file system access?

Yes, managing session-based learnings requires local file system access to the ~/.gstack/sessions directory and project-specific JSONL logs. This local storage mechanism maintains historical continuity for your engineering workflows.

What is the best way to export project insights for team documentation?

The best way to export project insights is to use the lifecycle management features to centralize accumulated learnings. You can then export this curated knowledge base directly for documentation or team sharing purposes.

Can I query past AI-assisted engineering sessions to find a previously diagnosed bug?

Yes, you can query past sessions to search for previously diagnosed and resolved bugs. The knowledge retrieval mechanism searches historical JSONL logs to provide context-aware insights and prevent repeating past mistakes.