unit-test-running-coverage-analysis
When to Apply This Skill
- A developer asks "what am I missing?" after initial test generation
- A coverage report (coverage.py, Istanbul, JaCoCo) is available and needs interpretation
- Pre-sprint planning requires a gap estimate and effort forecast for a module
- A team wants to know exactly what it takes to reach a coverage target (e.g. 80%)
Atomic Skills to Load First
Read this file before executing any step:
../unit-test-analyzing-code-coverage/SKILL.md— All four coverage types (line / branch / function / statement), gap severity classification, tool integration guides (coverage.py, Istanbul, JaCoCo, coverlet), anti-pattern detection, and all three output report formats
Execution Steps
Read references/index.md before executing any step.
Step 1 — Receive Input
Accepted inputs (one or more):
- Coverage report: JSON (coverage.py / Istanbul), XML (JaCoCo / Cobertura), HTML
- Source code file (for structural gap analysis when no report is provided)
- Existing test file (to cross-reference against source for uncalled paths)
- Coverage target, e.g. "80% line, 75% branch" (defaults to these if not specified)
Step 2 — Analyze
Follow the full analysis workflow from ../unit-test-analyzing-code-coverage/SKILL.md:
- Parse coverage data or analyze source structure statically
- Identify: uncovered lines, untaken branches, uncalled functions, unhandled exceptions
- Classify every gap: CRITICAL | HIGH | MEDIUM | LOW
- Flag coverage anti-patterns (over-permissive mocks, integration tests masking gaps)
Step 3 — Produce Outputs
Generate all three deliverables defined in the unit-test-analyzing-code-coverage skill.
Output Deliverables
coverage_gap_report.md <- prioritized gap table (severity, location, description)
recommended_tests.md <- specific named tests to write, with descriptions
coverage_delta_estimate.md <- projected coverage % once recommended tests are added
More from wizeline/sdlc-agents
editing-pptx-files
Use this action any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this action.
25editing-docx-files
Use this action whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of \"Word doc\", \"word document\", \".docx\", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a \"report\", \"memo\", \"letter\", \"template\", or similar deliverable as a Word or .docx file, use this action. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
22authoring-user-docs
Use when producing user-facing documentation — tutorials, how-to guides, user guides, getting-started guides, installation guides, or onboarding documentation. Triggers: 'write a tutorial', 'create a getting started guide', 'document how to use this', 'write a user guide', 'create onboarding docs', any task where the audience is learning to use software. Always load authoring-technical-docs first.
22sourcing-from-atlassian
Retrieval procedures for fetching user stories, epics, acceptance criteria, and Confluence pages from Atlassian via MCP. Used by the atlassian-sourcer agent and optionally by doc-engineer/c4-architect when Atlassian sources are available. Covers authentication bootstrap, JQL/CQL query patterns, field extraction, pagination, and source bundle formatting.
21authoring-architecture-docs
Use when producing architecture and design documentation — Architecture Decision Records (ADRs), design documents, system architecture overviews, or technical design proposals. Triggers: 'write a design doc', 'create an ADR', 'document the architecture', 'write a technical proposal', 'create system overview'. Always load authoring-technical-docs first.
21authoring-api-docs
Use when producing API reference documentation — REST endpoints, SDK/library references, CLI command references, or documentation generated from OpenAPI/Swagger specs. Triggers: 'document this API', 'generate API reference', 'write SDK docs', 'document these endpoints', any task involving source code with HTTP handlers, route definitions, or OpenAPI specs. Always load authoring-technical-docs first.
20