learning-log

Record development discoveries into a structured learning log file.

224|87|Updated Dec 15, 2018
One-click install
npx skills add https://github.com/Resgrid/Core --skill learning-log-resgrid
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: learning-log
Source: https://github.com/Resgrid/Core/tree/main/.opencode/skills/learning-log
Command: npx skills add https://github.com/Resgrid/Core --skill learning-log-resgrid

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of forgetting or losing valuable development insights—like root causes, tradeoffs, gotchas, and performance findings—by turning them into a searchable, consistent learning log.

Core Features & Use Cases

  • Track organic discoveries: Record non-obvious bug root causes, undocumented architecture decisions, gotchas, workarounds, and performance observations as they happen.
  • Keep entries searchable: Store each entry with a date, category, title, description, and affected files using a consistent format and category system.
  • Differentiate knowledge types: Maintain a clear separation between prescriptive corrective rules (MEMORY.md), session state handoff notes, and this descriptive learning archive.

Quick Start

Use the learning-log skill to document a non-obvious bug root cause by noting the real cause, how to avoid the confusion, and the affected files for that incident.

Frequently Asked Questions about learning-log

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

FAQPage Schema
How do I document debugging discoveries and architecture decisions for later review?

Document debugging discoveries and architecture decisions by capturing non-obvious root causes, tradeoffs, and gotchas into a structured learning log with categories, titles, descriptions, and affected files for searchable knowledge reuse.

What is the best way to track development discoveries separately from session handoff notes?

Tracking development discoveries separately from session handoff notes requires storing descriptive insights in a dedicated archive, differentiating them from prescriptive corrective rules and session state to maintain clear knowledge type separation.

Can I log performance findings and configuration surprises using a consistent format?

Yes, you can log performance findings and configuration surprises using a consistent entry structure that records dates, categories, titles, descriptions, and affected files, ensuring observations remain searchable and structured.

How does a learning log differ from prescriptive corrective rules in MEMORY.md?

A learning log differs from MEMORY.md by serving as a descriptive archive of organic discoveries like workarounds and external service behavior mismatches, whereas MEMORY.md stores prescriptive corrective rules for immediate application.

When do I need to record workaround documentation for external service behavior mismatches?

Record workaround documentation for external service behavior mismatches when you uncover non-obvious service interactions or gotchas, ensuring the root cause and affected files are structured for later review and knowledge reuse.