Maintains a per-repo Markdown findings file at ./context/findings.md across sessions.
npx skills add https://github.com/jmreicha/configs --skill findings
Please help me install this Agent Skill. Skill: findings Source: https://github.com/jmreicha/configs/tree/main/skills/findings Command: npx skills add https://github.com/jmreicha/configs --skill findings
This Skill helps teams maintain a per-repo findings file that tracks mistakes, corrections, and effective patterns, providing persistent context across sessions.
Read and initialize ./context/findings.md at the start of every session, then update it continuously as you work.
High-intent search queries and answers about installing and using this skill.
You can maintain a persistent log of mistakes and corrections by using a per-repo findings file at ./context/findings.md. This Markdown document is read at the start of every session and updated continuously to track patterns and guide future work.
A per-repo findings file is a Markdown document stored at ./context/findings.md that tracks mistakes, corrections, and effective patterns. It improves continuous learning by requiring sessions to read and update the log during work, providing persistent context across sessions.
To track session context and learnings within a specific repository, initialize a findings file at ./context/findings.md. Read the file at the start of each session and update it continuously as you work to capture effective patterns and corrections.
Yes, you can apply a continuous documentation log to any repository regardless of domain. The per-repo findings file at ./context/findings.md is domain agnostic and requires no dependencies to track corrections and improve processes over time.
The best way to capture user corrections during a development session is to maintain a findings file at ./context/findings.md. By updating this Markdown document continuously as you work, you ensure corrections and successful patterns are logged for future reference.
No dependencies or special components are needed to start logging session findings. The process simply requires reading and initializing a standard Markdown file at ./context/findings.md to track mistakes and patterns across sessions.
jinglemansweepCreate a .plans directory with a .gitkeep file at the repository root.
ambroviaAnalyze retro log files to identify recurring development frictions across work packages.
tanujsutariaAppend formatted entries to SESSION_LOG.md after detecting file changes.
johnlindquistCapture and organize coding lessons from sessions and reviews into reusable patterns.
