explain-code-slice

What problem does it solve?

Engineers and reviewers often need a faithful, stepwise explanation of how a single request, event, job, or datum moves through a system. This Skill removes ambiguity by identifying triggers, incoming data shapes, boundaries, branch points, and the exact transformations that occur so readers can follow the full execution path without gaps.

Core Features & Use Cases

• Provides an ordered, conversational walkthrough from trigger to final output with concrete callouts for where data changes shape.
• Highlights boundaries (module, process, service), branch points, and whether logic is shared or specialized so reviewers and debuggers can focus inspections.
• Supports direct comparisons between two slices or two implementations to show why behavior diverges and where changes occur.
• Useful for onboarding, code review walkthroughs, debugging request lifecycles, and documenting critical execution paths.

Quick Start

Explain the slice for saving a new reminder by starting with the incoming data shape and walking every meaningful step through validation, storage, and final UI update at standard detail.