test-debt
Surface test-suite debt — skipped tests, untested public APIs, flaky patterns (retries, sleeps), missing edge cases. Pattern-based static analysis; does not run coverage tools. Use when tests feel unreliable or before a release.
What this skill does
# Test Debt Surface debt in the test suite — what's skipped, what's untested, what's flaky by design. ## Philosophy > "What confidence are we missing, and which code changes are riskier because of it?" A test suite with a hundred skipped tests is lying to the team about what's covered. A retry loop in a test is telling you the real behavior isn't deterministic. Test debt is where the suite stops being a safety net. Not a coverage report. This skill is pattern-based — it reads test files and source files, and spots the gaps between them. Runtime coverage is a complementary tool, not this skill's job. ## Scope User specifies a path, glob, or directory. If not specified, ask: *"Which directory or test file should I audit?"* ## Config Integration Follow `references/config-migration.md` for preflight. Read `.assistant-config.md` for: - **Test location** (set by `/teach-charter`) - **Stack** (determines skip patterns per framework) - **Acknowledged Debt** ## Stack Detection Detect test framework from dev dependencies / manifest: - `jest`, `vitest`, `mocha`, `cypress`, `playwright` in `package.json` - `pytest` in `requirements.txt` / `pyproject.toml` - `rspec` in `Gemfile` - Built-in `testing` package for Go - `junit` / `testng` for JVM projects Use the right skip patterns. See `references/test-debt-patterns.md`. ## Process ### 1. Understand context Locate the test directory. Count test files. Note the framework in use. ### 2. Scan - **Skipped tests:** Grep for framework-specific skip markers. - **Flaky patterns:** Grep for retry loops, `sleep`/`setTimeout` inside test files, high timeouts. - **Untested public APIs:** Glob source, identify exported symbols (language-specific), cross-reference against test files. ### 3. Group by location Group by test file (for skips and flakiness) or by source module (for untested APIs). ### 4. Assess impact - **High:** skipped tests on critical paths, untested public APIs on entry points - **Medium:** flaky patterns in core test suites - **Low:** skipped tests with tracked issues, untested internal helpers ## Reference - `references/test-debt-patterns.md` - `references/debt-output-format.md` - `references/config-migration.md` ## Output format Follow `references/debt-output-format.md` exactly. ## What Makes This Different From a Linter A linter flags `it.skip` every time. This skill asks: *is this skip tracked, or is it an unowned promise? Is this retry loop legitimate, or is the test fighting non-determinism? Is this exported function genuinely untested, or transitively covered?* The value is the second-order read, not detection.
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.