record-recipe

Capture technical resolutions into structured markdown recipes for error pattern matching.

Updated May 5, 2026
One-click install
npx skills add https://github.com/iani-kuli/harness_bro --skill record-recipe-iani-kuli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: record-recipe
Source: https://github.com/iani-kuli/harness_bro/tree/main/.claude/skills/curated/record-recipe
Command: npx skills add https://github.com/iani-kuli/harness_bro --skill record-recipe-iani-kuli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of repetitive debugging by capturing successful technical fixes into a structured knowledge base, preventing the need to re-solve the same issues.

Core Features & Use Cases

  • Knowledge Persistence: Automatically saves problem-fix patterns into a structured recipe format.
  • Automated Suggestion: Integrates with auto-fix hooks to suggest known solutions when similar error patterns recur.
  • Use Case: After spending time resolving a complex CUDA out-of-memory error, use this skill to save the specific configuration fix so the AI can automatically apply it the next time the same error occurs.

Quick Start

Ask the assistant to record the recent fix as a recipe for the current error pattern.

Frequently Asked Questions about record-recipe

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

FAQPage Schema
How do I save successful debugging fixes into a knowledge base?

To save debugging fixes into a knowledge base, you can capture successful technical resolutions into structured markdown recipes, creating a repository of verified problem-fix patterns to prevent re-solving recurring issues.

How does pattern matching work for automated troubleshooting?

Automated troubleshooting uses regex-based pattern recognition to link stderr and stdout outputs to previously indexed fix procedures, allowing the system to automatically suggest known solutions when similar error patterns recur.

What is the best way to stop re-solving the same software development issues?

The best way to stop re-solving recurring software development issues is to record successful fixes into a structured recipe format, enabling knowledge persistence and automated error pattern matching for future occurrences.

Can I automate error pattern matching using stdout and stderr outputs?

Yes, you can automate error pattern matching by indexing stderr and stdout outputs with regex-based recognition, which links the error outputs directly to verified fix procedures stored in your markdown knowledge base.

How do I record a recent fix as a recipe for a current error pattern?

To record a recent fix as a recipe, simply ask the assistant to capture the specific configuration resolution, and it will save the problem-fix pattern into a structured markdown format for automated future retrieval.