test-coverage-advisor
Improve Rust Test Coverage
Missing tests leave Rust error paths and edge cases unprotected. This skill reviews code and tests, then suggests targeted coverage improvements.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "test-coverage-advisor" from https://skillstore.io/skills/emillindfors-test-coverage-advisor.md and its manifest at https://skillstore.io/api/skills/emillindfors-test-coverage-advisor/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "test-coverage-advisor". A validate_email function only has one success test.
Expected outcome:
Suggested coverage: empty input, missing at sign, missing domain, and a table of valid and invalid addresses.
Using "test-coverage-advisor". An async repository lookup has no failure tests.
Expected outcome:
Recommended tests: found user, missing user, repository error, and timeout or cancellation behavior if supported.
Using "test-coverage-advisor". A test module contains setup-heavy tests with no clear assertions.
Expected outcome:
Refactor guidance: split tests by behavior, keep one reason per test, and add explicit assertions for observable outcomes.
Security Audit
SafeThe static command findings are false positives caused by Markdown code fences in Rust and bash examples, not executable code. The blocker findings are sample email addresses in a table-driven test example. I found no evidence of prompt injection, data exfiltration, unauthorized network use, or tool instructions beyond Read/Grep/Glob.
Risk Factors
⚙️ External commands (25)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/emillindfors-test-coverage-advisor/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/emillindfors-test-coverage-advisor?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/emillindfors-test-coverage-advisor?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/emillindfors-test-coverage-advisor/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/emillindfors-test-coverage-advisor.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
EmilLindfors. (2026). test-coverage-advisor security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/emillindfors-test-coverage-advisor/audits/4BibTeX citation
@techreport{emillindfors-emillindfors-test-coverage-advisor-2026,
author = {EmilLindfors},
title = {test-coverage-advisor security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/emillindfors-test-coverage-advisor/audits/4},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "test-coverage-advisor security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "EmilLindfors"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/emillindfors-test-coverage-advisor/audits/4"
identifiers:
- type: other
value: "skillstore:emillindfors-test-coverage-advisor:audit:4"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Add Tests for New Rust Code
Identify missing success, failure, and boundary tests before a feature is merged.
Review Pull Request Coverage
Check whether a change includes enough tests for error paths and edge cases.
Plan Regression Coverage
Turn bug reports or risky behavior into focused regression test ideas.
Try These Prompts
Review this Rust function and suggest missing success, error, and edge case tests: [paste code].
Review this Rust test module. Identify missing assertions, error paths, and opportunities for table-driven tests: [paste tests].
Analyze this async Rust API and propose tests for success, failure, timeout, and not-found behavior: [paste code].
Assess this feature implementation and tests. Prioritize the highest-risk missing cases and explain why each test matters: [paste files or summary].
Best Practices
- Share the smallest relevant function or test module so suggestions are specific.
- Include expected error types and business rules when asking for coverage advice.
- Ask for prioritized gaps when a feature has many possible edge cases.
Avoid
- Using the skill as a substitute for running test and coverage tools.
- Asking for broad coverage advice without showing code or behavior rules.
- Accepting generated test ideas without checking domain correctness.
Frequently Asked Questions
Does this skill run coverage tools?
Which language is it designed for?
Can it write full tests?
Does it detect every missing edge case?
Can it help with existing tests?
Is it safe to use with private code?
Developer Details
Author
EmilLindforsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
a06681402992ceae98ba04d54cfd4ab004862696
Maintenance freshness
7/18/2026
Usage
5 downloads · 226 views
File structure
📄 SKILL.md