toolchain-review

To analyze session friction from script execution failures, review the current session context to identify toolchain friction points like non-zero exit codes, tracebacks, and repeated retries. This process categorizes issues by severity to highlight what blocks development.

The best way to debug environment mismatches is to aggregate error signals like ImportError and non-zero exit codes from your session. Categorizing these environment mismatches into severity levels P0, P1, and P2 pinpoints exactly what blocks your build.

Generate a structured report for toolchain errors by summarizing retry signs and tracebacks from your session. The tool outputs a timestamped report to the local .temp/report directory, categorizing script errors and detours into P0, P1, and P2 severity levels.

Yes, you can use session analysis to classify unclear skill instruction steps. The session review identifies friction from unclear steps alongside script failures and environment mismatches, categorizing all these issues into P0, P1, and P2 severity levels.

You need a toolchain review when repeated failures, detours, or environment mismatches slow down your development actions. If you are unsure why your script execution keeps failing, a session review identifies the root cause and prioritizes fixes.

Categorizing session friction into P0, P1, and P2 levels helps debugging by prioritizing the most critical toolchain errors first. This severity grading clarifies which script execution failures or environment mismatches require immediate attention over minor detours.