Agent skill · software engineering · ailabs-393

test-specialist

This skill should be used when writing test cases, fixing bugs, analyzing code for potential issues, or improving test coverage for JavaScript/TypeScript applications. Use this for unit tests, integration tests, end-to-end tests, debugging runtime errors, logic bugs, performance issues, security vulnerabilities, and systematic code analysis.

Why this skill is useful

Provides structured testing methodologies and debugging techniques specific to JavaScript/TypeScript applications that the AI wouldn't reliably generate on its own.

What it needs

About 7k tokens when loaded. Last updated 2025-11-11. 438 stars on the source repository.

What this skill does

Test Specialist Overview Apply systematic testing methodologies and debugging techniques to JavaScript/TypeScript applications. This skill provides comprehensive testing strategies, bug analysis frameworks, and automated tools for identifying coverage gaps and untested code. Core Capabilities 1. Writing Test Cases Write comprehensive tests covering unit, integration, and end-to-end scenarios. Unit Testing Approach Structure tests using the AAA pattern (Arrange-Act-Assert): Key principles: Test one behavior per test Cover happy path, edge cases, and error conditions Use descriptive test names that explain the scenario Keep tests independent and isolated Integration Testing Approach Test how components work together, including database, API, and service interactions: End-to-End Testing Approach Test complete user workflows using tools like Playwright or Cypress: 2. Systematic Bug Analysis Apply structured debugging methodology to identify and fix issues. Five-Step Analysis Process 1. Reproduction: Reliably reproduce the bug Document exact steps to trigger Identify required environment/state Note expected vs actual behavior 2. Isolation: Narrow down the problem Binary search through code path Create minimal reproduction case Remove unrelated dependencies 3. Root Cause Analysis: Determine underlying cause Trace execution flow Check assumptions and preconditions Review recent changes (git blame) 4. Fix Implementation: Implement solution Write failing test first (TDD) Implement the fix Verify test passes 5. Validation: Ensure completeness Run full test suite Test edge cases Verify no regressions Common Bug Patterns Race Conditions: Null/Undefined Errors: Off-by-One Errors: 3. Identifying Potential Issues Proactively identify issues before they become bugs. Security Vulnerabilities Test for common security issues: Performance Issues Test for performance problems: Logic Errors Use parameterized tests to catch edge cases: 4. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills ailabs-393/test-specialist

View the source on GitHub

Browse the @skills marketplace