[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-1)Run the tests in verbose mode and read the outputs carefully. Then inspect any of the files that have changed that might be causing issues. If you need to explore and read files to figure out what might be going on, we are also able to use Git to identify when these issues may have arisen.
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-2)
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-3)For each failing test:
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-4)1. Extract the stack trace and identify the exact line causing the failure
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-5)2. Use git blame on that line to see who last modified it and when
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-6)3. Check git log for recent commits touching those files
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-7)4. Look at related test files that might share similar patterns
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-8)5. If it's an import/dependency error, check package.json or requirements.txt changes
[](https://jxnl.co/writing/2025/08/29/context-engineering-slash-commands-subagents/#__codelineno-1-9)6. Summarize findings in a structured format: test name, root cause hypothesis, suspect commits, and recommended fix