skills.rest
dannys-code-corner
dannys-code-cornerOFFICIAL
Explore all skills by this author →
GitHub

review-test-style

Review touched tests for style issues and coverage gaps.

92|7|Updated Dec 11, 2025
Search Tags:#rust#compiler#quality-assurance#test-coverage#style-analysis#test-review#slice-report
One-click install
npx skills add https://github.com/dannys-code-corner/incan --skill review-test-style
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-test-style
Source: https://github.com/dannys-code-corner/incan/tree/main/.agents/skills/review-test-style
Command: npx skills add https://github.com/dannys-code-corner/incan --skill review-test-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review touched tests and test-adjacent code for style, Result-returning patterns, panic helpers, unwrap/expect use, and obvious coverage gaps. Use when a broad review needs a dedicated test pass or when the user asks for test-review specifically.

Core Features & Use Cases

  • Detect common anti-patterns in tests such as excessive unwrap/expect usage, panic-driven control flow, and missing targeted coverage.
  • Produce a concise slice report (.agents/state/review-report.test-style.md) with concrete recommendations for test improvements.
  • Provide a scoped, repeatable review workflow that can be invoked on demand or as part of a CI checklist.

Quick Start

Run the review pass on the current workspace changes to generate a focused test-style feedback slice.

Frequently Asked Questions about review-test-style

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

FAQPage Schema
How do I check test coverage gaps and style issues in recently modified Rust code?▼

To check test coverage gaps and style issues in touched Rust code, apply a focused review pass that analyzes recently modified components and generates a slice report with actionable recommendations.

What are common anti-patterns to look for during a Rust test review?▼

Common Rust test review anti-patterns include excessive unwrap and expect usage, panic-driven control flow, missing targeted coverage, and improper Result-returning patterns in test-adjacent code.

How do I generate a test-style slice report for my workspace changes?▼

Generate a test-style slice report by running a review pass on your current workspace changes, which produces a focused markdown file containing concrete recommendations for test improvements.

Can I use this test review pass as part of a CI checklist?▼

Yes, you can use this scoped and repeatable test review workflow as part of a CI checklist by invoking the review on demand to verify changes against existing test coverage and project standards.

Does the test review analyze the entire project or just recently modified components?▼

The test review limits its analysis to recently modified components, ensuring findings are scoped strictly to the changes under review and verified against existing test coverage and project standards.

Why should I run a dedicated test-style review instead of a broad code review?▼

A dedicated test-style review is necessary when a broad review needs a specific test pass, focusing exclusively on test coverage gaps, panic helpers, and style issues that general reviews often miss.

Related Skills

Explore More Software Engineering Skills→
majedsiefalnasrmajedsiefalnasr

post-implementation-simplification

Remove dead code and consolidate duplicates in task-touched files.

Community
Intermediate
TobiasBakTobiasBak

course-report-analyzer

Map student report sections to course lectures and identify coverage gaps.

Community
Advanced
dorriodorrio

ln-741-linter-configurator

Configure ESLint, Prettier, Ruff, mypy, and .NET analyzers for projects.

Community
Basic
aidottersaidotters

validation

Analyze Python projects with ruff, mypy, and pytest for style, type, and coverage.

Community
Intermediate