What problem does it solve? Teams repeatedly hit the same failures across builds, packaging, recovery, and release work because previously learned lessons are not checked before acting. This Skill provides a public catalog of known error fingerprints so engineers can force-check an intended path against documented failures before repeating them. ## Core Features & Use Cases - Mandatory preflight contract: Before consequential build, debug, test, verify, recovery, packaging, or release work, compare the intended tool, runtime, platform, and symptom against the catalog and classify the result as NO KNOWN MATCH, POSSIBLE MATCH, KNOWN ERROR / MITIGATION AVAILABLE, KNOWN ERROR / CONDITIONS CHANGED, or STOP. - 27 documented error fingerprints: Covers PowerShell parser and stderr pitfalls, Windows path length and normalization issues, Python bytecode residue, Git bundle ref assumptions, manifest exclusion bugs, rollback verification gaps, version metadata drift, trust enforcement gaps, and more, each with prevention guidance and a do-not-repeat rule. - Use Case: Before running a newly generated PowerShell packaging script on Windows, check the catalog, find KE-PS-PARSER-GENERATED-SCRIPT-001, and parser-validate the exact final .ps1 file before execution instead of debugging a preventable syntax failure. ## Quick Start Before my next build or release step, check the known-errors catalog and tell me whether my planned action matches any documented error fingerprint and what mitigation to apply.
