Regression Diagnosis

Full FREE body

Copy Back to Kimi Code

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

### Regression Diagnosis
TYPE: KIMI CODE
PURPOSE: Perform the “Regression Diagnosis” 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 “Regression Diagnosis” 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 “Regression Diagnosis”:
- Restate success for regression diagnosis in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute regression diagnosis; reject unrelated material.
- Call out code/design risks unique to regression diagnosis; do not invent files.
- Produce the artifact a practitioner would expect from regression diagnosis.
- Self-check: does every claim serve regression diagnosis? Remove filler.
- End with next verification specific to regression diagnosis.
QUALITY CHECKS:
- Specific to supplied material and to “Regression Diagnosis”.
- 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 “Regression Diagnosis”.
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