Unit Test Coverage Helper
Requirement
Use this skill to help maintainers and users asking for software improvements with:
feat:Add Unit Tests
Read references/requirement-plan.md when source evidence, planning details, or review criteria are needed.
Workflow
- Restate the user's outcome, constraints, available inputs, and success criteria.
- Convert the request into a practical plan and useful output.
- Ask only for missing information that materially changes the output; otherwise make reasonable assumptions and continue.
- Produce the requested artifact, workflow, checklist, analysis, code change, or decision support.
- Validate the output against the success criteria and list any remaining risks or follow-up work.
Expected Outputs
- A tailored answer or artifact for the user's immediate situation.
- A reusable checklist or workflow when the task is repeatable.
- A verification note showing how the result was checked.
Validation
- The output directly addresses the discovered requirement.
- The user can act on the result without reading the original source post.
- Assumptions, limits, and required inputs are visible.
- The final response includes a short usage or next-step note when helpful.
Triggers
Keywords: general-help, add, unit, tests, labels, gssoc, level, intermediate, type
Example trigger sentences:
Help me Add Unit Tests.I need a practical workflow for Add Unit Tests.Use $unit-test-coverage-helper to handle Add Unit Tests.