ワンクリックでManusで任意のスキルを実行

checking-test-coverage

スター0

フォーク0

更新日2026年3月24日 17:49

Analyze test coverage gaps and suggest targeted tests for uncovered code paths. Use when evaluating test adequacy, identifying missing edge case tests, or improving confidence before a release.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

musher-dev

musher-dev/bundles

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Checking Test Coverage

Analyze a codebase or changeset to identify gaps in test coverage and recommend targeted tests that maximize confidence.

Analysis Approach

1. Identify What Changed

Map the files and functions modified in the changeset
Determine which are business logic vs. configuration vs. infrastructure

2. Trace Code Paths

For each modified function:

Identify the happy path and verify it has a test
Identify error/exception paths and check for corresponding tests
Identify boundary conditions (empty inputs, max values, type coercion) and check coverage
Identify interactions with external systems (databases, APIs, filesystems) and check for integration tests

3. Evaluate Existing Tests

Do tests assert behavior (what the code does) rather than implementation (how it does it)?
Are test names descriptive enough to serve as documentation?
Do tests cover the specific scenarios introduced by this change?
Are there tests that need updating due to changed behavior?

4. Recommend New Tests

For each coverage gap, suggest a specific test:

Name the test clearly: test_<function>_<scenario>_<expected_outcome>
Describe the setup, action, and assertion
Prioritize tests that catch regressions over tests that verify obvious behavior

Prioritization

Focus testing effort where it matters most:

Critical path — authentication, authorization, payment processing, data persistence
Error handling — failure modes that affect users or data integrity
Edge cases — boundary values, empty states, concurrent access
Integration points — external API calls, database queries, message queues

Output

Produce a summary with:

Coverage assessment (which paths are tested, which are not)
Prioritized list of recommended tests with descriptions
Any existing tests that should be updated or removed

このリポジトリの他の Skills

同じリポジトリ

summarizing-changes

musher-dev/bundles

Summarize git history, staged diffs, or PR changes into clear, human-readable summaries grouped by theme.

2026-04-020

writing-commit-messages

musher-dev/bundles

Generate Conventional Commits-compliant commit messages from staged changes or a description of work done.

2026-04-020

building-code-displays

musher-dev/bundles

Build marketing-grade code displays for the Musher marketing site -- split-panel code-then-output layouts, CSS-only syntax highlighting, tabbed views, and terminal chrome. Use when implementing IA Section 3 (Mechanism), building code blocks, creating terminal demos, highlighting YAML/CLI output, or adding copy buttons to code. Triggered by: code display, code block, syntax highlighting, code-then-output, split panel code, terminal chrome, YAML highlight, CLI output, code snippet, tabbed code, multi-language code, mechanism section code, bundle yaml, pipeline yaml, marketing code.

2026-04-020

scaffolding-sections

musher-dev/bundles

Scaffold marketing page sections from IA definitions into Svelte 5 components. Use when building section components from the Information Architecture, translating archetypes to markup, mapping content slots to elements, or creating section scaffolds. Triggered by: scaffold section, build section, IA to component, section component, hero section, mechanism section, value grid, proof block, community block, CTA block, social proof bar, content slot, archetype component, layout pattern, section scaffold, marketing component.

2026-04-020

csv-insights

musher-dev/bundles

Analyze CSV data by computing aggregations, filtering rows, and generating readable summaries. Use when working with tabular data files in a container environment where the agent creates and manipulates files directly.

2026-04-020

aligning-ci-environments

musher-dev/bundles

Ensure local development environments match CI/CD environments for consistent behavior including shared version sources, devcontainer reuse in CI, reproducible dependency installation, environment variable parity, Docker image sharing, and lock file enforcement. Use when diagnosing works-on-my-machine issues, designing CI pipelines that mirror local dev, or auditing environment parity. Triggered by: CI alignment, CI environment, works on my machine, CI parity, environment parity, CI local match, GitHub Actions, CI pipeline, CI docker, reproducible builds, lock file, frozen lockfile.

2026-03-270

Checking Test Coverage

Analyze a codebase or changeset to identify gaps in test coverage and recommend targeted tests that maximize confidence.

Analysis Approach

1. Identify What Changed

Map the files and functions modified in the changeset

Determine which are business logic vs. configuration vs. infrastructure

2. Trace Code Paths

For each modified function:

Identify the happy path and verify it has a test

Identify error/exception paths and check for corresponding tests

Identify boundary conditions (empty inputs, max values, type coercion) and check coverage

Identify interactions with external systems (databases, APIs, filesystems) and check for integration tests

3. Evaluate Existing Tests

Do tests assert behavior (what the code does) rather than implementation (how it does it)?

Are test names descriptive enough to serve as documentation?

Do tests cover the specific scenarios introduced by this change?

Are there tests that need updating due to changed behavior?

4. Recommend New Tests

For each coverage gap, suggest a specific test:

Name the test clearly: test_<function>_<scenario>_<expected_outcome>

Describe the setup, action, and assertion

Prioritize tests that catch regressions over tests that verify obvious behavior

Prioritization

Focus testing effort where it matters most:

Critical path — authentication, authorization, payment processing, data persistence

Error handling — failure modes that affect users or data integrity

Edge cases — boundary values, empty states, concurrent access

Integration points — external API calls, database queries, message queues

Output

Produce a summary with:

Coverage assessment (which paths are tested, which are not)

Prioritized list of recommended tests with descriptions

Any existing tests that should be updated or removed

name	checking-test-coverage
description	Analyze test coverage gaps and suggest targeted tests for uncovered code paths. Use when evaluating test adequacy, identifying missing edge case tests, or improving confidence before a release.