learner

To turn debugging insights into reusable decision heuristics, this Skill extracts the underlying decision-making principle from a specific incident, requiring the exact error context, precise fix, and recognition triggers to generalize the workaround for future Claude Code sessions.

The best way to capture hard-won workarounds is by extracting the non-obvious behavior into a generalized skill with mandatory YAML frontmatter, ensuring the specific problem statement, exact solution details, and precise recognition triggers are documented for future error recognition.

To save extracted debugging knowledge for project-aware reuse, this Skill helps choose between user-level and project-level storage strategies, ensuring learned decision rules are preserved appropriately in the correct context for similar future failures.

Yes, this knowledge extraction approach uses quality validation gates to prevent saving generic or easily Googleable guidance by requiring specific error context, precise fixes, and strong recognition triggers before a heuristic is finalized.

To extract a reusable debugging skill, you need to provide the exact error message, relevant file path and line numbers, the precise fix you made, and the recognition triggers you expect to encounter in similar future debugging failures.

You should not use automated skill extraction for debugging incidents where the fix is obvious, easily searchable, or lacks hidden gotchas, as the quality validation gates require specific non-obvious behavior and strong recognition triggers to justify saving a heuristic.