log-learning

An AI-powered tool that monitors your driving behavior and rewards you for staying off your phone.

Updated Jul 13, 2024

Search Tags:#documentation #knowledge management #learning #progress #development log #codebase patterns

Ready to run

npx skills add https://github.com/bearbinary/Jarvy --skill log-learning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: log-learning
Source: https://github.com/bearbinary/Jarvy/tree/main/.claude/skills/log-learning
Command: npx skills add https://github.com/bearbinary/Jarvy --skill log-learning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you retain valuable insights gained during development, preventing knowledge loss and accelerating future work sessions by maintaining a persistent log of your progress and discoveries.

Core Features & Use Cases

Capture Codebase Patterns: Document recurring structural or behavioral patterns in the code.
Record Task Completion: Log what was implemented, files changed, and key learnings after finishing a task.
Note Gotchas & Warnings: Save encountered issues or unexpected behaviors for future reference.
Document Decisions: Record the rationale behind important architectural or design choices.
Use Case: While working on a new feature, you discover a common pattern for handling authentication middleware. You log this pattern, along with a note about a tricky gotcha you encountered with the logging library. The next day, when you start a new task, you can quickly review these logs to refresh your memory and avoid repeating past mistakes.

Quick Start

Log a new codebase pattern you discovered to the progress file.

Frequently Asked Questions about log-learning

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

FAQPage Schema

How do I log codebase patterns and development progress for future recall?▼

To log codebase patterns and development progress, you record structured markdown entries into a persistent `progress.txt` file at your project root, capturing task completion notes, gotchas, and architectural decisions for later knowledge retention and recall.

What is the best way to document development gotchas and architectural decisions?▼

The best way to document development gotchas and architectural decisions is maintaining a persistent progress file that stores structured markdown entries, preventing knowledge loss and accelerating future work sessions through reliable knowledge management.

How do I record task completion notes and key learnings in a markdown file?▼

You record task completion notes by appending structured markdown entries detailing files changed and key learnings to a `progress.txt` file, ensuring insights are captured immediately for iterative development workflows.

Does this development log require any specific dependencies or external tools?▼

No, this development log requires no external dependencies or tools. It operates by writing structured markdown entries directly into a `progress.txt` file located at the project root for persistent knowledge management.

Can I use this logging method for iterative development workflows?▼

Yes, you can use this logging method for iterative development workflows. It facilitates knowledge retention by allowing you to quickly review past codebase patterns and warnings, refreshing your memory before starting new tasks.

What are the limitations of using a single progress.txt file for knowledge management?▼

Using a single `progress.txt` file limits knowledge management to basic structured markdown entries at the project root. It lacks advanced search or database features, relying entirely on manual markdown organization for recalling development logs.