Review unit and integration test quality in the FitnessApp project. Use when the user asks to review tests, check test quality, analyze test coverage, assess testability, find test gaps, or improve test structure. Covers Swift Testing (@Test/@Suite) and FitnessTestSupport conventions.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "reviewing-test-quality" with this command: npx skills add Jose-Luis-Nunez/skillsmp-jose-luis-nunez-jose-luis-nunez-reviewing-test-quality
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Scaffold a new SwiftUI feature module, extend an existing feature, or create a picker sheet with correct project conventions. Use when the user asks to create a new feature, screen, page, module, view, tab, picker, calendar, schedule, dashboard, settings, or add functionality to an existing feature. Also use when asked to build a neue Seite, neues Feature, neuer Screen, new screen, or new page in the FitnessApp iOS project.
Update, refactor, or modernize existing XCUITest UI tests in the FitnessApp project. Use when the user asks to update, refactor, modernize, or clean up an existing UI test, or when a test is outdated or uses wrong patterns. For tests that fail or have selectors that cannot be found, use `debugging-ui-tests` instead.
Create new XCUITest UI tests for the FitnessApp project. Use when the user asks to create, write, or add a new UI test, test a new feature, add test coverage for a screen, or add accessibility identifiers for testing.
Diagnose and fix failing XCUITest UI tests in the FitnessApp project. Investigate selector-not-found errors, scheme/build-config issues, fixture seeding mismatches after SwiftData refactors, and timing flakes. Use when a UI test fails, when a selector is not found, when investigating timeout errors, or when production-code changes broke UITestLaunchStrategy or test-fixture seeding.