hmem-new-error

Create hmem E-entries with a six-section scaffold from a title and description.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-new-error
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hmem-new-error
Source: https://github.com/YuryZZZ/opencode-global/tree/main/skills/hmem-new-error
Command: npx skills add https://github.com/YuryZZZ/opencode-global --skill hmem-new-error

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and log new error entries (E-entries) in hmem to persist bugs, errors, and problems in long-term memory with a standardized workflow.

Core Features & Use Cases

  • Six-section auto-scaffold: Analysis, Possible fixes, Fixing attempts, Solution, Cause, Key Learnings, generated automatically from a minimal input.
  • No-manual-E-entries rule: Enforces the correct usage and prevents ad-hoc logging; provides a strict format and frontmatter validation.
  • Easy integration: Works with existing hmem memory pipeline to ensure consistent tracking and retrieval of issues.

Quick Start

Log a new error using the hmem-new-error skill to create an E-entry in memory.

Frequently Asked Questions about hmem-new-error

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

FAQPage Schema
How do I log bug entries in long-term memory with a standardized format?

You log bug entries by providing a title and plain description, which triggers auto-scaffolding of six sections—Analysis, Possible fixes, Fixing attempts, Solution, Cause, Key Learnings—to persist errors in long-term memory.

What is the no-tabs rule for creating error entries in memory?

The no-tabs rule enforces strict formatting by rejecting tab characters in plain descriptions, ensuring consistent discovery and memory integrity when creating error entries.

Can I create error entries manually without the six-section scaffold?

No, the no-manual-E-entries rule prevents ad-hoc logging by enforcing a strict six-section scaffold and fixed frontmatter with name and description, ensuring consistent memory tracking and retrieval.

Do I need to fill out all six sections when documenting an error?

No, the system auto-creates the six sections from minimal input, requiring only a title and plain description to generate the full Analysis, Possible fixes, Fixing attempts, Solution, Cause, and Key Learnings scaffold.

What's the best way to track fixing attempts and solutions in persistent memory?

Track fixing attempts and solutions by logging a new error entry, which auto-scaffolds dedicated sections for Fixing attempts, Solution, Cause, and Key Learnings to persist problems in long-term memory.

Why does my error entry description fail frontmatter validation?

Description validation fails when tab characters are included, violating the no-tabs rule, or when the fixed frontmatter with name and description is missing or incorrectly formatted for memory integrity.