resolve-failed-test
Analyze a failed test, fix the underlying issue, and verify the fix. Use after /test reports failures.
What this skill does
# Resolve Failed Test
Analyze a failed test, fix the underlying issue, and verify the fix.
## Variables
- `test_result`: $ARGUMENTS - JSON object from /test command with failed test details
## Input Format
Expects a JSON object from the /test command:
```json
{
"test_name": "unit_tests",
"passed": false,
"execution_command": "pytest tests/test_auth.py -v",
"test_purpose": "Validates authentication functionality",
"error": "AssertionError: Expected status 200, got 401"
}
```
## Instructions
### 1. Analyze the Test Failure
Review the test result:
- **test_name**: Which test category failed
- **test_purpose**: What functionality is being validated
- **error**: The specific error message
- **execution_command**: How to reproduce
Identify the root cause by understanding:
- What was expected vs. what happened
- Which code path likely failed
- Possible causes of the error
### 2. Reproduce the Failure
**IMPORTANT**: Use the exact `execution_command` from the test result:
```bash
# Run the exact command to confirm failure
{execution_command}
```
Verify you see the same error. This ensures you're fixing the right problem.
### 3. Fix the Issue
Apply a fix following these principles:
- **Minimal changes**: Fix only what's broken
- **Fix the code, not the test**: Tests verify correctness
- **Preserve existing behavior**: Don't introduce regressions
- **Match existing patterns**: Follow codebase conventions
### 4. Validate the Fix
Re-run the exact same execution_command:
```bash
{execution_command}
```
**Success criteria**: Test now passes (exit code 0, no failures)
### 5. Run Full Validation
If the specific test passes, run the full test suite to check for regressions:
```bash
# Run complete test suite
[full test command]
```
## Output Format
Report your resolution:
```markdown
## Resolution Complete
### Failure Analysis
- **Test**: {test_name}
- **Root Cause**: [What caused the failure]
- **Error**: {error}
### Fix Applied
- **File(s) Modified**: [list of files]
- **Change Summary**: [brief description]
### Validation
- **Specific Test**: PASS
- **Full Suite**: PASS/FAIL
- **Command Used**: {execution_command}
### Notes
[Any observations or recommendations]
```
## Retry Logic
If the fix doesn't work:
1. Re-analyze the error output
2. Consider alternative root causes
3. Apply a different fix
4. Re-validate
Maximum 3 retry attempts before escalating.
## Integration with Closed Loop
This command is the **RESOLVE** phase:
```text
/test → [failure JSON] → /resolve-failed-test {result} → /test
↓
[verify fix]
```
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.