القائمة
Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill check-coverageيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Project initialization inventory (one-time). Use when: first onboarding a project, rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-explore). Output: project map with entrypoints + test map + next steps.
Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.
Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | check-coverage |
| description | Comprehensive assessment of Unit / Integration / E2E three-layer test coverage, identify gaps and provide actionable recommendations. |
| allowed-tools | Read, Grep, Glob, Bash(ls:*), Bash(find:*), Bash(wc:*), Agent |
/codex-test-review)/codex-test-gen)/verify)See @skills/test-review/SKILL.md for Codex-based test review workflow.
Agent({
description: "Assess three-layer test coverage and identify gaps",
subagent_type: "coverage-analyst",
prompt: `Assess Unit / Integration / E2E test coverage for the feature docs at: $ARGUMENTS
Follow the steps defined in this skill.`
})
Read specified feature docs. Extract:
Search related source code based on feature documentation. Build source code inventory.
Check whether each source file has corresponding tests (unit, integration, e2e).
For each source file:
| Severity | Description |
|---|---|
| 🔴 Critical | Core logic, data writes, amount calculations |
| 🟠 Major | Important branches, error handling |
| 🟡 Minor | Edge cases, utility functions |
| ⚪ Nice-to-have | Logging, formatting |
# Test Coverage Analysis Report
## Feature Overview
- Feature name: <from documentation>
- Documentation path: $ARGUMENTS
- Related modules: <list>
## Current Coverage
| Module | Source Path | Test Path | Coverage Status |
|--------|------------|-----------|----------------|
## Coverage Gaps
### 🔴 Critical
### 🟠 Major
### 🟡 Minor
## Recommended New Tests
| Priority | Test Type | Test Case | Target File |
|----------|-----------|-----------|-------------|
## Coverage Summary
| Metric | Status |
|--------|--------|
| Feature coverage | X/Y (Z%) |
| Happy path | ✅/❌ |
| Error path | ✅/❌ |
| Edge cases | ✅/❌ |