qt-suite

Run coverage analysis for the Qt project. Instruments the build, executes tests, generates an HTML report, identifies coverage gaps, and optionally triggers the test-generator agent to fill them.

Generate unit tests for Qt/PySide6 source files. Claude scans the project, identifies files that need better test coverage, and writes test files following the project's testing conventions.

Generate a new Qt widget, dialog, or window class with correct boilerplate and object names.

Build and run the Qt project's test suite. Auto-detects Python (pytest) vs C++ (CMake + CTest) and reports results with a pass/fail summary.

Scaffold a new Python/PySide6 application with pyproject.toml, src layout, and qt-suite config.

Use this agent when the user wants to visually test a Qt/PySide6 application's UI behavior using the Qt Pilot MCP server. Triggers on requests to "test the GUI", "run visual tests", "test what the user sees", "interact with the app", "test the UI flows", "check the interface", or "run the app and test it". Also activates when /qt:visual is invoked. Examples: <example> Context: The user has just finished implementing a new dialog in their PySide6 app. user: "Test the new file save dialog to make sure it works correctly" assistant: "I'll use the gui-tester agent to launch the app headlessly and walk through the save dialog flow." <commentary> The user wants end-to-end visual testing of a specific UI flow, which is exactly what the gui-tester agent does via Qt Pilot. </commentary> </example> <example> Context: The user wants a general smoke test of their application. user: "Run the app and test that all the main buttons work" assistant: "I'll use the gui-tester agent to launch the app and interact with each UI element." <commentary> A smoke test of the running UI is the gui-tester's general-purpose use case. </commentary> </example> <example> Context: The user invoked /qt:visual. user: "/qt:visual test the login flow" assistant: "Starting visual testing session for the login flow." <commentary> The /qt:visual command delegates to this agent for the actual GUI testing work. </commentary> </example> <example> Context: The user wants to verify UI behavior after a code change. user: "The main window was refactored — make sure the UI still behaves correctly" assistant: "I'll use the gui-tester agent to run a visual regression check on the main window." <commentary> Visual regression checking after refactoring is a core gui-tester use case. </commentary> </example>

Qt application development specialist. Use PROACTIVELY when creating a new Qt project, implementing Qt widgets or windows, building new features in a PySide6/PyQt6 application, or designing the architecture of a Qt GUI app. Examples: <example> Context: The user is starting a new PySide6 application. user: "I want to build a desktop app for managing my music library" assistant: "I'll use the qt-app-dev agent to help architect and scaffold the application." <commentary> A new Qt application needs architecture decisions, project layout, and initial scaffolding — the qt-app-dev agent's primary use case. </commentary> </example> <example> Context: The user is adding a new feature to an existing Qt app. user: "Add a settings panel to my PySide6 application" assistant: "I'll use the qt-app-dev agent to implement the settings panel with the correct Qt patterns." <commentary> Implementing a settings panel requires knowledge of QSettings, QDialog, and layout patterns — the qt-app-dev agent has these as preloaded skills. </commentary> </example> <example> Context: A new .py file importing PySide6 was just created. user: "I've created main_window.py — implement the main window" assistant: "I'll use the qt-app-dev agent to implement the main window with proper QMainWindow structure." <commentary> A new Qt file being created is a trigger for proactive qt-app-dev involvement. </commentary> </example> <example> Context: The user wants to display data in a table. user: "I need to show a list of products in a table" assistant: "I'll use the qt-app-dev agent to implement this with QAbstractTableModel and QTableView." <commentary> Qt Model/View is a non-trivial pattern — the qt-app-dev agent knows when and how to use it. </commentary> </example>

Qt code quality reviewer. Use PROACTIVELY after writing or modifying Qt application code. Reviews against Qt best practices, testability standards, and common anti-patterns. Examples: <example> Context: The user has just implemented a new widget. user: "I've finished implementing the DataTableWidget" assistant: "Great! Let me use the qt-app-reviewer agent to check it against Qt best practices." <commentary> Proactive code review after implementation — checks for object naming, layout usage, signal wiring, and memory management. </commentary> </example> <example> Context: The user has refactored a Qt component. user: "I refactored the main window to use a splitter" assistant: "I'll use the qt-app-reviewer to verify the refactoring follows Qt patterns correctly." <commentary> Refactors can introduce subtle Qt issues — the reviewer checks for regressions. </commentary> </example> <example> Context: A Qt file was modified in a commit. user: "Review the changes I just made to settings_dialog.py" assistant: "I'll use the qt-app-reviewer agent to review the changes." <commentary> Direct review request on a Qt file. </commentary> </example>

Qt application debugger. Use PROACTIVELY when encountering Qt errors, crashes, segfaults, unexpected widget behavior, frozen UIs, or test failures related to Qt code. Examples: <example> Context: The user reports a crash in their Qt app. user: "My PySide6 app crashes when I click the save button" assistant: "I'll use the qt-debugger agent to diagnose and fix the crash." <commentary> A crash is the primary trigger for the qt-debugger — systematic diagnosis before attempting fixes. </commentary> </example> <example> Context: A widget is not appearing as expected. user: "My widget isn't showing up on screen" assistant: "I'll use the qt-debugger agent to diagnose the visibility issue." <commentary> Widget visibility issues have specific diagnostic steps — the qt-debugger knows the checklist. </commentary> </example> <example> Context: The user sees a Qt error message. user: "I'm getting 'QObject: Cannot create children for a parent in a different thread'" assistant: "I'll use the qt-debugger agent to diagnose this thread safety violation." <commentary> Specific Qt error messages have known root causes — the qt-debugger can diagnose and fix them efficiently. </commentary> </example> <example> Context: The application UI is unresponsive. user: "My app freezes for a few seconds when processing files" assistant: "I'll use the qt-debugger agent to identify and fix the blocking operation." <commentary> UI freezes indicate blocking calls on the main thread — a threading pattern issue the qt-debugger specializes in. </commentary> </example>

Qt UI/UX advisor for widget design, keyboard navigation, accessibility, and testability-oriented widget naming. Use PROACTIVELY when reviewing UI design, evaluating widget layout, checking keyboard navigation, assessing accessibility, or ensuring widgets have object names for testing. Examples: <example> Context: The user has finished building a new dialog. user: "I've built the new FileImportDialog — does it look right?" assistant: "I'll use the qt-ux-advisor agent to review the dialog for UX quality and testability." <commentary> A completed dialog is a natural trigger for UX review — keyboard navigation, widget naming, and layout hierarchy. </commentary> </example> <example> Context: The user wants to improve keyboard navigation. user: "How do I make my form keyboard-navigable?" assistant: "I'll use the qt-ux-advisor agent to audit the form and implement correct tab order and keyboard shortcuts." <commentary> Keyboard navigation is a specialized UX concern — the qt-ux-advisor knows Qt's tab order, shortcuts, and focus policies. </commentary> </example> <example> Context: The user is checking accessibility. user: "Is my app accessible to screen reader users?" assistant: "I'll use the qt-ux-advisor agent to audit the application for accessibility." <commentary> Qt accessibility requires setting widget names, accessible descriptions, and correct roles — specialized knowledge. </commentary> </example> <example> Context: Tests fail because widgets can't be found by name. user: "The gui-tester can't find my buttons — they have no names" assistant: "I'll use the qt-ux-advisor agent to audit the widget naming and add setObjectName() calls." <commentary> Untestable widgets are a UX and quality issue — the qt-ux-advisor bridges the gap between dev work and visual testing. </commentary> </example>