test
Run project test suite and report results in structured JSON format. Use to validate implementation before commit or review.
What this skill does
# Application Validation Test Suite
Run the project's test suite and report results in structured JSON format.
## Purpose
Proactively identify issues in the application before they impact users. This command executes the validation stack and reports results for automated processing.
## Instructions
1. **Detect Project Type**: Look for package.json, pyproject.toml, or other config files
2. **Identify Test Commands**: Find the appropriate test runner and commands
3. **Execute Tests in Sequence**:
- Lint check
- Type check (if applicable)
- Unit/integration tests
- Build verification
4. **Capture Results**: Record pass/fail status and any error messages
5. **Return JSON**: Output only the structured JSON array
## Test Execution Sequence
Execute each validation command in order:
1. **Lint Check** - Code style and syntax validation
2. **Type Check** - Type safety verification (TypeScript, Python with mypy)
3. **Unit Tests** - Core functionality tests
4. **Build** - Production build verification
**IMPORTANT**: If a test fails, stop processing and return results thus far.
## Output Format
Return ONLY a JSON array with test results:
```json
[
{
"test_name": "lint_check",
"passed": true,
"execution_command": "npm run lint",
"test_purpose": "Validates code style and syntax",
"error": null
},
{
"test_name": "type_check",
"passed": true,
"execution_command": "npx tsc --noEmit",
"test_purpose": "Validates TypeScript types",
"error": null
},
{
"test_name": "unit_tests",
"passed": false,
"execution_command": "npm test",
"test_purpose": "Validates core functionality",
"error": "FAIL tests/auth.test.ts - Expected 200, received 401"
}
]
```
## Result Structure
Each test result includes:
| Field | Description |
| --- | --- |
| `test_name` | Identifier for the test category |
| `passed` | Boolean - true if test passed |
| `execution_command` | Exact command to reproduce |
| `test_purpose` | What this test validates |
| `error` | Error message if failed, null if passed |
## Sorting
Sort the JSON array with failed tests (`passed: false`) at the top.
## Integration with Closed Loop
This command is the **REQUEST** phase of a closed loop:
```text
/test → [JSON results] → /resolve-failed-test {result}
```
The structured output enables automated resolution.
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.