Record successful technical fixes as reusable debugging recipes.
npx skills add https://github.com/yanochka11/harness_bro --skill record-recipe
Please help me install this Agent Skill. Skill: record-recipe Source: https://github.com/yanochka11/harness_bro/tree/main/.claude/skills/curated/record-recipe Command: npx skills add https://github.com/yanochka11/harness_bro --skill record-recipe
This Skill prevents repeated debugging work by turning successful technical fixes into reusable memory recipes that can be discovered and applied later.
Use the record-recipe skill to save the successful fix from the current debugging session into reusable project memory.
High-intent search queries and answers about installing and using this skill.
To save debugging fixes as reusable memory, you record solved issues as structured recipes containing the problem, fix, and rationale. This updates the project memory index so future debugging workflows can automatically discover and apply the saved solutions.
The best way to prevent repeated debugging work is to capture successful technical fixes as structured recipes. By preserving the problem, fix, and rationale in a memory index, recurring errors like dependency issues or configuration failures can be resolved using previously proven solutions.
Yes, you can automate the retrieval of known software fixes. By updating the project memory index with structured recipe files, future debugging workflows can use pattern-based discovery to automatically find and suggest matching solutions for recurring errors.
To record a resolved dependency or configuration failure, you capture the issue as a structured recipe file with problem, fix, and rationale sections. This updates the project memory index, preserving the engineering knowledge for pattern-based discovery.
Yes, saving debugging recipes requires structured recipe files formatted with problem, fix, and rationale sections. This structure supports pattern-based discovery and updates the memory index so future debugging workflows can retrieve the engineering knowledge effectively.
You should preserve engineering knowledge as debugging recipes when recurring errors or configuration failures have proven fixes that need long-term retrieval. Structured recipes update the memory index for pattern-based discovery, unlike inline comments which lack automated future session integration.
bketelsenCondense session memory and decision logs into durable summaries.
dmzoneillSave error patterns with fixes and categories into a persistent memory store.
boomNDSAutomate GitHub workflows with AI-assisted PR reviews, issue triage, and CI/CD integration.
MarcoAntoliniConvert conversation context into a Product Requirements Document and integrate it into an issue tracker.
