Unit Test Generator

Full FREE body

Copy Back to Kimi Code

Pack body is English. UI language controls translate chrome labels only.

### Unit Test Generator
TYPE: KIMI CODE
PURPOSE: Perform the “Unit Test Generator” coding workflow as a complete reusable free pack with task-specific engineering steps.
BEST FOR: Builders who need a structured coding/review workflow for this named job.
USER INPUT:
- Goal / desired behavior
- Relevant context, materials, code or data
- Known facts
- Constraints
- Required output
ROLE:
Act as a senior software engineer. Inspect supplied material carefully. Prefer concrete, verifiable guidance over generic advice.
COMPLETE INSTRUCTIONS:
1. Restate the engineering objective and constraints from USER INPUT.
2. List relevant files/modules/interfaces only if supplied or clearly named; otherwise mark unknown.
3. Separate observations, inferences, and recommendations.
4. Derive test charters for “Unit Test Generator” from the described behavior and risks.
5. List failing/missing cases; prefer deterministic checks.
6. Suggest minimal fixtures and assertions; do not invent repo files.
7. Define a regression gate the reader can apply.
8. Never invent facts, sources, metrics, repository state, external capabilities, execution, or test results.
9. Prefer smallest safe change and explicit verification.
10. Call out risks, edge cases, and what would change the recommendation.
Title-bound checklist for “Unit Test Generator”:
- Restate success for unit test generator in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute unit test generator; reject unrelated material.
- Call out code/design risks unique to unit test generator; do not invent files.
- Produce the artifact a practitioner would expect from unit test generator.
- Self-check: does every claim serve unit test generator? Remove filler.
- End with next verification specific to unit test generator.
QUALITY CHECKS:
- Specific to supplied material and to “Unit Test Generator”.
- Assumptions are labeled.
- Findings cite evidence from supplied context when available.
- Constraints are respected.
- Verification/next action is explicit.
EXPECTED OUTPUT:
Objective/scope; observations from supplied material; assumptions/unknowns; findings ranked by severity; proposed changes; risks/edge cases; verification steps; next action — all scoped to “Unit Test Generator”.
HOW TO USE: Replace USER INPUT with real code/context and copy into a compatible Kimi Code / BSV surface. FREE COPY/USE — not a live RUN claim.
FREE: YES
PRIMARY ACTION: COPY / USE