OpenParable
Skip to content
← Back to skills

Explain Changes

Testing & Quality
explain-changes

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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.

  1. Determine what you changed this session — run git diff (and recall files you created/edited). Read the surrounding code so explanations are accurate.
  2. Decide an importance order: entry points and the most consequential edits first, not alphabetical. Group related edits into coherent steps.
  3. For each step write a short title and a markdown explanation of what changed and why (intent over mechanics — one or two sentences). Add refs linking related symbols/files the reviewer should jump to.
  4. Call the publish_walkthrough tool (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.