hf-bug-patterns

Identifies recurring mistakes and drafts a bug pattern candidate for human confirmation.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/hujianbest/garage-agent --skill hf-bug-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hf-bug-patterns
Source: https://github.com/hujianbest/garage-agent/tree/main/packs/coding/skills/hf-bug-patterns
Command: npx skills add https://github.com/hujianbest/garage-agent --skill hf-bug-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill captures recurring mistakes from reviews, hotfixes, and conversations and codifies them into reusable bug patterns, ensuring human confirmation before cataloging.

Core Features & Use Cases

  • Identify recurring mistakes across multiple tasks and sessions to surface patterns.
  • Abstract patterns with identifiable signals, prevention steps, and validation guidance.
  • Enforce human-in-the-loop gating before writing to the bug-pattern catalog.
  • Provide a workflow template and references to template docs to facilitate cataloging.

Quick Start

Review a recurring issue in a sprint and generate a candidate bug-pattern draft for human approval.

Frequently Asked Questions about hf-bug-patterns

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

FAQPage Schema
How do I turn recurring engineering mistakes into reusable bug patterns?

You identify recurring mistakes across sessions and draft a candidate bug pattern containing evidence, signals, and upgrade criteria, pausing for human confirmation before cataloging.

What is a human-in-the-loop bug pattern cataloging workflow?

A human-in-the-loop bug pattern workflow extracts recurring mistakes from reviews and hotfixes, drafts a pattern with prevention steps, and strictly enforces human confirmation before writing to the bug-pattern catalog.

How do I identify recurring mistakes across multiple development sessions?

You identify recurring mistakes across multiple sessions by abstracting the issues into identifiable signals and prevention steps, then drafting a provisional pattern statement for team review.

What signals should I watch for when drafting a bug pattern candidate?

When drafting a bug pattern candidate, watch for signals described in the evidence, outline specific prevention steps, and define validation guidance to move from a candidate to a full catalog entry.

Can I automatically write recurring engineering mistakes to a bug-pattern catalog?

No, you cannot automatically write to the bug-pattern catalog because the workflow enforces human-in-the-loop gating, requiring explicit human confirmation before any candidate is officially cataloged.