error-interpretationlisted

# Error Interpretation ## What This Skill Enables Agents with this skill can diagnose failures methodically by reading what the system is actually telling them. Without it, agents fall into shotgun debugging -- trying random fixes, changing multiple things at once, and hoping something sticks. A skilled agent reads the error, forms a hypothesis, and verifies it before writing a single line of corrective code. ## Core Competencies ### 1. Read the Actual Error Message First This sounds obvious but is the most commonly skipped step. Before doing anything: 1. Copy the **full** error output, not just the first line. 2. Identify the **error type or code** (e.g., `TypeError`, `ECONNREFUSED`, `HTTP 403`, exit code 137). 3. Identify the **error message** (the human-readable explanation after the type). 4. Note any **file path and line number** referenced. ``` # Example: Don't just see "TypeError". Read the whole thing. TypeError: Cannot read properties of undefined (reading 'map') at renderList (src/components/UserList.tsx:14:22) at processChild (node_modules/react-dom/cjs/react-dom.development.js:1234:12) # What to extract: # Type: TypeError # Message: Cannot read properties of undefined (reading 'map') # Where: src/components/UserList.tsx, line 14, column 22 # What: Something is undefined when .map() is called on it ``` ### 2. Parse Stack Traces Correctly Stack traces list frames from most recent call to oldest. Your job is to find the boundary bet