lc-explain

Generate Markdown explanations for solved LeetCode problems from Rust solutions.

Updated Jan 6, 2026

Search Tags:#documentation #markdown #analysis #rust #explanation #leetcode

Ready to run

npx skills add https://github.com/iQeda/MyRust-NeetCode --skill lc-explain

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: lc-explain
Source: https://github.com/iQeda/MyRust-NeetCode/tree/main/.claude/skills/lc-explain
Command: npx skills add https://github.com/iQeda/MyRust-NeetCode --skill lc-explain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

LeetCode Explain automates the creation of structured Markdown explanations for solved LeetCode problems by translating Rust solutions into clear, human-friendly notes.

Core Features & Use Cases

Generate a detailed explanatory document for a given LeetCode problem.
Outline the problem, the approach, algorithm steps, and code excerpts.
Output to explanation/problems/<problem_id>.<problem-name>.md to integrate with your documentation workflow.

Quick Start

Run /lc-explain <problem_id> to generate the explanation for that problem.

Frequently Asked Questions about lc-explain

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

FAQPage Schema

How do I generate Markdown explanations for LeetCode solutions?▼

To generate Markdown explanations for LeetCode solutions, run /lc-explain <problem_id>. The tool scans your problems/ directory, parses the Rust code, and outputs a formatted documentation file to explanation/problems/.

Can I automatically document my Rust LeetCode solutions?▼

Yes, you can automatically document Rust LeetCode solutions by parsing the code to identify the approach and algorithm steps. It translates the logic into structured Markdown notes for your documentation workflow.

What is the best way to create structured notes from solved LeetCode problems?▼

The best way to create structured notes from solved LeetCode problems is to automate the extraction of algorithm steps from Rust code. This enforces a required Markdown template to ensure consistent documentation.

Do I need to write my Rust solutions in a specific directory for documentation generation?▼

Yes, you need to place your Rust solutions in the problems/ directory. The documentation generation tool scans this specific folder to find solution files and parse their algorithmic approach.

Does the generated LeetCode explanation include code excerpts and approach outlines?▼

Yes, the generated LeetCode explanation includes code excerpts and approach outlines. It outlines the problem, the approach, algorithm steps, and code excerpts in the Markdown file.

Where are the generated Markdown files saved in my documentation workflow?▼

The generated Markdown files are saved under explanation/problems/<problem_id>.<problem-name>.md. This output path ensures compatibility with your existing documentation workflow.