test-gotcha-review

Analyze modified tests against a repository-specific gotcha checklist and report findings.

1|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Jaggia/backTestingTraderBot --skill test-gotcha-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-gotcha-review
Source: https://github.com/Jaggia/backTestingTraderBot/tree/main/.claude/skills/test-gotcha-review
Command: npx skills add https://github.com/Jaggia/backTestingTraderBot --skill test-gotcha-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-commit test quality check specific to this codebase. Identify and flag known gotchas in tests before committing, or when asked to review tests.

Core Features & Use Cases

  • Walks modified tests (git diff) against a predefined gotcha checklist derived from the repository.
  • Reports per-file and per-line findings with actionable fixes and references.
  • Supports targeted scope via explicit ARGUMENTS to review specific test files or classes.

Quick Start

Run /test-gotcha-review after staging tests to review for repo-specific gotchas.

Frequently Asked Questions about test-gotcha-review

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

FAQPage Schema
How do I check pytest tests for repository-specific gotchas before committing?

To check pytest tests for repository-specific gotchas before committing, run the test-gotcha-review process against your staged git diff. It analyzes modified tests using a predefined checklist of known failure modes and outputs structured guidance with suggested fixes.

What is a pre-commit test review and how does it identify false positives?

A pre-commit test review identifies false positives by walking modified tests against a predefined gotcha checklist derived from the codebase. It reports per-file and per-line findings with actionable fixes and references to prevent missed bugs before code is committed.

Can I review specific test files or classes instead of the entire git diff?

Yes, you can review specific test files or classes by providing explicit ARGUMENTS to the review process. This targeted scope allows you to analyze only the modified tests you specify against the predefined gotcha checklist.

What's the best way to enforce code quality checks for known test failure modes?

The best way to enforce code quality checks for known test failure modes is to run a pre-commit review that applies a predefined repository-specific checklist to your modified tests, generating structured guidance with file and line references to ensure codebase consistency.