review-test-style

Review tests and adjacent code for style and coverage gaps.

92|7|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/encero-systems/incan --skill review-test-style-encero-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-test-style
Source: https://github.com/encero-systems/incan/tree/main/.agents/skills/review-test-style
Command: npx skills add https://github.com/encero-systems/incan --skill review-test-style-encero-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a focused review of tests and test-adjacent code to identify style issues, Result-returning patterns, panic helpers, unwrap/expect usage, and coverage gaps.

Core Features & Use Cases

  • Test Style Review: Analyze tests for common style issues and coverage gaps.
  • Result-Returning Patterns: Identify where unwrap() and expect() should be replaced with Result and assertions.
  • Panic Helper Analysis: Flag panic!-driven control flow that could be clearer with Result + assertions.
  • Use Case: Use this Skill during a code review to ensure tests are comprehensive and adhere to best practices.

Quick Start

Run the review-test-style skill on your code changes to automatically check for style and coverage issues in your tests.

Frequently Asked Questions about review-test-style

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

FAQPage Schema
How do I review test code for unwrap and expect usage during code reviews?▼

You can review test code for unwrap and expect usage by running a targeted test style review that identifies unwrap/expect calls and suggests replacing them with Result-returning patterns and assertions to improve test quality.

What is a panic helper in test code and when should it be replaced?▼

A panic helper is panic!-driven control flow used in tests that should be replaced when clearer Result-based assertions provide better error messages and test structure. Targeted test review flags these patterns automatically.

How do I identify test coverage gaps in touched code during continuous integration?▼

To identify test coverage gaps in touched code during continuous integration, run a focused review on changed tests and adjacent code that analyzes Result-returning patterns and flags missing coverage for potential improvements.

Does test style review work without external dependencies or plugins?▼

Yes, test style review works without external dependencies because it uses built-in scripts to analyze touched tests and adjacent code for style issues, coverage gaps, and unwrap/expect usage without requiring additional plugins.

What's the best way to enforce Result-returning patterns in test suites?▼

The best way to enforce Result-returning patterns in test suites is to run an automated review that detects unwrap/expect usage and panic helpers, then flags where Result types and assertions should replace them for clearer test logic.

When should I not use automated test style review on my codebase?▼

Automated test style review may not be ideal when tests intentionally use panic-driven control flow for specific scenarios or when existing test conventions require unwrap/expect patterns that should not be refactored to Result-returning approaches.