---
author: 'Matheus Rocha'
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.'
extras:
  'Add a reviewer and non-technical audience eval to prove the explanation
  adapts without speculation.'
focus: 'Explain changed code faithfully for the intended reader.'
id: 'generated-code-explanation'
improve:
  - 'The named demo-project module paths make the skill trigger too broadly
    outside that project; move them to a project reference.'
  - 'Ask for the diff or paths before explaining an unprovided change.'
  - 'Avoid requiring “alternatives considered” unless evidence supports them.'
name: 'generated-code-explanation'
path: '../submitted-skills/Matheus%20Rocha/skills/generated-code-explanation/SKILL.md'
status: 'Good writing guide'
title: 'Generated code explanation'
wins:
  - 'The what/why/verify structure is clear.'
  - 'Explicitly prohibits invented rationale.'
---

# 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.
