code-walkthrough

Trace call chains and data flow across Tauri Rust and React codebases.

10|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/tincopper/neeko --skill code-walkthrough-tincopper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-walkthrough
Source: https://github.com/tincopper/neeko/tree/main/.agents/skills/code-walkthrough
Command: npx skills add https://github.com/tincopper/neeko --skill code-walkthrough-tincopper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you read and understand Neeko’s codebase without getting lost, turning a large Tauri plus React application into a clear, evidence-based architecture walkthrough.

Core Features & Use Cases

  • Architecture Exploration: Map Rust backend layers, React frontend layers, and the bridge between them.
  • Call Chain Tracing: Follow an entry point through commands, managers, hooks, events, and UI updates.
  • Code Review Support: Spot dead code, type mismatches, design drift, and migration gaps while reading.
  • Use Case: Ask for a walkthrough of the terminal, git, or skill-management flow to understand how data moves across the app.

Quick Start

Ask for a walkthrough of the specific Neeko module, file, or function you want to understand.

Frequently Asked Questions about code-walkthrough

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

FAQPage Schema
How do I trace a call chain across a Tauri Rust backend and React frontend?

To trace a call chain across a Tauri Rust backend and React frontend, request a walkthrough of a specific entry point to follow commands, managers, hooks, events, and UI updates with file-and-line evidence. This maps the complete data flow across endpoints.

What's the best way to understand a large Tauri and React application architecture?

Understanding a large Tauri and React application architecture is best done through evidence-based code walkthroughs that map Rust backend layers, React frontend layers, and the bridge between them without modifying the codebase.

Can I detect dead code and type mismatches while reviewing a React and Rust codebase?

You can detect dead code, type mismatches, and design drift during a non-mutating code review by checking type contracts and tracing file-and-line references throughout the module exploration process.

How does code walkthrough help with debugging cross-endpoint bridge analysis?

Code walkthrough helps with debugging cross-endpoint bridge analysis by tracing data flow from entry points through commands and events, providing file-and-line evidence to pinpoint type-contract failures and migration gaps.

Do I need a non-mutating review environment to analyze Neeko code architecture?

A non-mutating review environment is required to analyze Neeko code architecture, ensuring the codebase remains unchanged while you map terminal, git, or skill-management flows and check for design drift.

Why does my terminal or git module flow have a data movement issue in a Tauri app?

A data movement issue in a terminal or git module flow within a Tauri app often stems from type-contract mismatches or design drift across the Rust and React bridge, which evidence-based call chain tracing can expose.