Marcos Silva
24 lines
889 B
Markdown
24 lines
889 B
Markdown
---
|
|
name: generated-code-explanation
|
|
description: Explain a code change, its supported rationale, trade-offs, and verification for a named audience. Use when a user asks what changed, why it changed, or how to validate it.
|
|
---
|
|
|
|
# generated-code-explanation
|
|
|
|
## Inputs
|
|
A diff, files, or a confirmed description of the change; intended audience.
|
|
|
|
## Workflow
|
|
1. Read the supplied code or diff before making claims.
|
|
2. Explain behavior first, then the evidence-backed reason and trade-offs.
|
|
3. Adapt vocabulary and depth to the audience.
|
|
4. State verification that was run and checks that remain.
|
|
|
|
## Rules
|
|
- Mark unknown intent as unknown; do not infer motivation.
|
|
- Do not add comments or documentation only to make an explanation easier.
|
|
- Read project-specific conventions from a reference only in that project.
|
|
|
|
## Output
|
|
Use: What changed, Why this approach, Trade-offs, How to verify.
|