followup-tests

Evaluate proposed changes to identify new tests, test modifications, or static analysis checks.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/cwilliams5/Alt-Tabby --skill followup-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: followup-tests
Source: https://github.com/cwilliams5/Alt-Tabby/tree/main/.claude/skills/followup-tests
Command: npx skills add https://github.com/cwilliams5/Alt-Tabby --skill followup-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps ensure that software changes are thoroughly tested and that potential issues are caught early through static analysis, improving overall code quality and reducing regressions.

Core Features & Use Cases

  • Test Gap Identification: Analyzes proposed changes to determine if new tests are needed or existing ones should be modified.
  • Static Analysis Suggestions: Recommends new static analysis checks to catch bugs at the code level before runtime.
  • Use Case: After a developer plans a new feature, this Skill can be used to review the plan and identify specific tests or code checks that should be implemented to validate the new functionality and prevent future bugs.

Quick Start

Review the current plan and evaluate whether they suggest new tests, test modifications, or new static analysis checks.

Frequently Asked Questions about followup-tests

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

FAQPage Schema
How do I identify missing test coverage after making code changes?

Static analysis suggestions evaluate recent code modifications to recommend new static analysis checks that catch bugs at the code level before runtime. This ensures potential issues are detected early during the development cycle, improving overall code quality.

What's the best way to maintain a fast and reliable test suite during regression testing?

Regression testing evaluates proposed changes to maintain a fast, parallelized, and reliable test suite. It identifies necessary test modifications and static analysis checks, ensuring batch or standalone execution adheres to best practices while catching potential regressions early.

When do I need to add new static analysis checks to my code review process?

Static analysis checks are needed when proposed code changes introduce patterns that existing checks do not cover. The evaluation process identifies gaps in current static analysis rules and recommends new checks to catch bugs at the code level before runtime.

Can I use test gap identification for both new features and modifications to existing tests?

Test gap identification works for both new features and existing test modifications. It analyzes proposed changes to determine whether completely new tests should be implemented or if current tests need adjustments to properly validate the modified functionality.

Does static analysis work with batch execution or only standalone test runs?

Static analysis supports both batch and standalone execution modes. The evaluation adheres to static analysis best practices for either execution type, ensuring reliable code checks whether running integrated batch processes or isolated standalone test suites.