Run any Skill in Manus with one click

explain-changes

Stars619

Forks92

UpdatedJune 29, 2026 at 21:56

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

astashov

astashov/liftosaur

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	explain-changes
description	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.

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

More from this repository

same repository

add-exercise

astashov/liftosaur

Add a new built-in exercise to Liftosaur end-to-end — image (gymvisual.com → S3), catalog registration, description page, and the LLM/MCP exercise list. Use when adding one or more built-in exercises to the app catalog.

2026-07-10619

liftoscript

astashov/liftosaur

Write idiomatic Liftoscript code for weightlifting programs. Use when creating or editing program files in programs/builtin/.

2026-07-10619

test-app

astashov/liftosaur

Manually test/QA the Liftosaur app on the iOS simulator — drive the real UI, inspect live app state, and set up test data. Use when asked to test, QA, stress-test, verify a change works, reproduce a bug, or hunt for bugs in the running app.

2026-07-01619

debug-rollbar

astashov/liftosaur

Interactively investigate a production Rollbar error. Accepts an occurrence id, item id, item counter, or Rollbar URL. Fetches the error data, assesses how widespread it is, drills into affected users (events, logs, storage, captured state), and works with the developer toward a fix or ignore decision. Use for collaborative debugging; use /fix-rollbar for a straight fetch-and-fix of a single occurrence.

2026-06-06619

debug-user

astashov/liftosaur

Investigate a user-reported issue using server logs, user events, storage snapshots, and Rollbar. Use when given a user id or email plus an issue description (e.g. from a support email).

2026-06-06619

fix-rollbar

astashov/liftosaur

Fix a production exception from Rollbar in an interactive Claude Code session. Fetches the occurrence data, analyzes the error, and either implements a fix or adds the error to the ignore list. Use when given a Rollbar occurrence ID.

2026-05-17619

name	explain-changes
description	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.

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