agentleFS
Sign inStart free
qimen039-codeqimen039-code/claim-boundary-harness/skills/bug-solution-memory/SKILL.md

bug-solution-memory

Skill2 starsChanged 28 days agoMITView on GitHub

Use when a specific stored Codex/local-tooling solution needs source validation, or the user authorizes saving an incident solution. Ordinary debugging and sufficient native recall do not require this record workflow.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Create a free account to mount
Files
SKILL.md

Bug Solution Memory

This file starts empty by design. Add real solution records only after the corresponding incident is understood.

Pairing Rule

  • Solution records live here.
  • Agent error records live in agent-error-memory.
  • Each solution point must include paired_error_ids.

Storage Contract

The table and field list below document the record shape; they are not the writable memory store. New records use cbh.semantic_memory_record.v3 and are appended with ../embedded-harness/semantic_memory.py to the adopting lane's private memory-v3/ directory. The canonical records.jsonl is append-only; meta.jsonl is a compact, rebuildable navigation surface. Existing Markdown records, when present in an older deployment, stay read-only and are exposed through hash-bound legacy links instead of being copied or rewritten.

Reference Index Shape

Solution IDOuter retrieval surfacePaired errors
SOL-EXAMPLE-YYYY-MM-DDexample solution trigger wordsERR-EXAMPLE-YYYY-MM-DD

Draft Field Guide

## SOL-EXAMPLE-YYYY-MM-DD

status:
point_kind: bug_solution_solid_point
purpose_anchor:
meaning_anchor:
outer_retrieval_surface:
problem_class:
solution_summary:
investigation_order:
fix_path:
rollback:
validation:
caveats:
applicable_boundaries:
non_applicable_boundaries:
paired_error_ids:
future_reuse_rule:
references:

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free