diagnostics-and-tooling

What problem does it solve?

This Skill eliminates guesswork when assessing the health, performance, and correctness of the Cambridge Beer Festival Flutter app, replacing subjective eyeballing of test results, crash traces, and toolchain behavior with concrete, reproducible measurements from official project tooling.

Core Features & Use Cases

• Test and analyze log capture: Run Flutter test and analyze tasks, capture their full output to timestamped log files, and grep for failures, errors, or warnings without re-running entire test suites.
• Production crash stack decoding: Decode minified Flutter web crash stacks from production or CI builds back to original Dart source file and line numbers, with built-in handling for CI vs local line offsets.
• Coverage triage: Summarize lcov coverage reports to identify under-covered source files, aligned with the project's 70% Codecov project and patch thresholds.
• Headless page and console probing: Run headless Chromium checks for page load success, capture full-page screenshots, and flag console errors for e2e test validation.
• Toolchain issue diagnosis: Use mise introspection commands to isolate whether task failures stem from code issues or misconfigured toolchain versions and environments. Use case example: If a CI e2e test fails with a minified web stack trace, use this skill to decode the stack to the exact Dart file and line causing the crash, or if a PR's coverage drops below the Codecov gate, use the lcov summary to identify which new or modified files lack test coverage.

Quick Start

Use the diagnostics-and-tooling skill to decode a minified Flutter web crash stack from a production CI build to find the exact Dart source file and line causing the error.