Release Verification Checklist

Full FREE body

Copy Back to Kimi Code

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

### Release Verification Checklist
TYPE: KIMI CODE
PURPOSE: Perform the “Release Verification Checklist” 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. Interpret “Release Verification Checklist” as an engineering workflow and stay in scope.
5. Inspect supplied code/context systematically.
6. Produce actionable findings with severity and next steps.
7. Do not invent repository state or command output.
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 “Release Verification Checklist”:
- Restate success for release verification checklist in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute release verification checklist; reject unrelated material.
- Call out code/design risks unique to release verification checklist; do not invent files.
- Produce the artifact a practitioner would expect from release verification checklist.
- Self-check: does every claim serve release verification checklist? Remove filler.
- End with next verification specific to release verification checklist.
QUALITY CHECKS:
- Specific to supplied material and to “Release Verification Checklist”.
- 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 “Release Verification Checklist”.
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