analyze-tests

Analyzes software test suites for quality gaps and improvement opportunities.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/lgtm-hq/claude-skills --skill analyze-tests-lgtm-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: analyze-tests
Source: https://github.com/lgtm-hq/claude-skills/tree/main/skills/analyze-tests
Command: npx skills add https://github.com/lgtm-hq/claude-skills --skill analyze-tests-lgtm-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers analyze the quality, structure, and effectiveness of a project's test suite, identifying areas for improvement and ensuring testing standards are met.

Core Features & Use Cases

  • Test Quality Assessment: Review overall test organization and adherence to best practices, such as SOLID and DRY principles.
  • Identify Weaknesses: Detect trivial tests, missing parameterization, complex code, and large or poorly structured test files.
  • Ensure Hygiene: Check for flaky tests, proper mocking, naming clarity, and setup/teardown practices.
  • Coverage Evaluation: Highlight gaps in edge case testing and integration point coverage.
  • Use Case: A QA engineer examines a test suite to pinpoint flaky tests and optimize test execution time, improving reliability and developer confidence.

Quick Start

Perform an analysis of the test code in the provided project repository to identify issues and suggest improvements.

Frequently Asked Questions about analyze-tests

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I evaluate test suite quality and identify missing test coverage?

Evaluating test suite quality involves reviewing test files for organization, coverage metrics, and code quality. This process detects trivial tests, missing parameterization, and complex code structures to highlight edge case gaps and integration point weaknesses.

What are common signs of weak test suite structure and poor test hygiene?

Weak test suite structures exhibit flaky tests, improper mocking, and unclear naming conventions. Identifying these issues involves checking for trivial tests, missing parameterization, and large poorly structured files that violate SOLID and DRY principles.

How do I analyze a project repository for flaky tests and missing parameterization?

Analyzing a project for flaky tests requires reviewing test files to check setup and teardown practices alongside mocking accuracy. This assessment detects missing parameterization and complex code to optimize execution time and improve reliability.

Can I check if my test files follow SOLID and DRY best practices during code review?

Yes, checking test files for SOLID and DRY adherence is a core part of test quality assessment. This review detects trivial tests, complex code, and large poorly structured files that deviate from established testing standards and best practices.

What is the best way to pinpoint test coverage gaps for edge cases and integration points?

The best way to pinpoint coverage gaps is to analyze the test suite structure to evaluate edge case testing and integration point coverage. This highlights missing parameterization and ensures comprehensive project quality assurance and reliability.