explain-code-slice

Trace code execution paths and data-shape transformations for bounded code slices.

6|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/gaelic-ghost/socket --skill explain-code-slice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-code-slice
Source: https://github.com/gaelic-ghost/socket/tree/main/plugins/productivity-skills/skills/explain-code-slice
Command: npx skills add https://github.com/gaelic-ghost/socket --skill explain-code-slice

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about explain-code-slice

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace a single datum through a system end-to-end?

Tracing a datum end-to-end requires identifying triggers, incoming data shapes, boundaries, and branch points. This Skill produces a step-ordered walkthrough with a compact diagram, showing exact data-shape transformations from trigger to final output.

What is the best way to compare two code implementations during a code review?

Comparing two implementations is best done by walking bounded code slices side by side. This Skill identifies where behavior diverges and highlights boundary callouts and data-shape changes, showing exactly why logic differs between the two paths.

How do I explain a request lifecycle for onboarding new engineers?

Explaining a request lifecycle involves providing a conversational, ordered walkthrough from trigger to output. This Skill identifies entrypoints, notes module boundaries, and details data-shape changes so new engineers can follow the full execution path without gaps.

How do I debug an event handler execution path with missing data transformations?

Debugging an event handler path requires tracking incoming data shapes and branch points. This Skill walks the bounded code slice step-by-step, marking where data changes shape and calling out boundaries so you can pinpoint exactly where transformations fail.

Can I walk through a specific function entrypoint to understand branch points?

Yes, you can walk through a specific function entrypoint by applying this Skill to a bounded code slice. It produces a step-ordered walkthrough that highlights branch points, shared versus specialized logic, and data-shape changes across the execution path.

Does this approach work for tracing feature flows across different services?

Tracing feature flows across services works by identifying process boundaries and branch callouts. This Skill walks the code slice end-to-end, producing a compact diagram with markers that notes where data shapes change as logic crosses module or service boundaries.