Explain Changes
Testing & Qualityexplain-changesExplain Changes is an Agent Skill for testing & quality published in the astashov/liftosaur repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Generate an importance-ordered guided walkthrough of your changes this session and publish it to the reviewer's editor via the aireviewer publish_walkthrough tool. Use when the user asks you to explain, walk through, or give a tour of your changes.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/astashov/liftosaur/blob/HEAD/.claude/skills/explain-changes/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/explain-changes, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Explain changes
Produce a guided tour of the code you changed this session so the reviewer can step through it in their editor.
- Determine what you changed this session — run
git diff(and recall files you created/edited). Read the surrounding code so explanations are accurate. - Decide an importance order: entry points and the most consequential edits first, not alphabetical. Group related edits into coherent steps.
- For each step write a short
titleand a markdownexplanationof what changed and why (intent over mechanics — one or two sentences). Addrefslinking related symbols/files the reviewer should jump to. - Call the
publish_walkthroughtool (aireviewer MCP server) with{ title, steps: [{ file, startLine, endLine, title, explanation, importance?, refs? }] }. All lines are 1-based and paths are workspace-relative.
Prefer 3–8 steps. After publishing, tell the user the tour is ready to start in VS Code.