Generate Markdown explanations for solved LeetCode problems from Rust solutions.
npx skills add https://github.com/iQeda/MyRust-NeetCode --skill lc-explain
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
LeetCode Explain automates the creation of structured Markdown explanations for solved LeetCode problems by translating Rust solutions into clear, human-friendly notes.
Run /lc-explain <problem_id> to generate the explanation for that problem.
High-intent search queries and answers about installing and using this skill.
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/.
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.
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.
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.
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.
The generated Markdown files are saved under explanation/problems/<problem_id>.<problem-name>.md. This output path ensures compatibility with your existing documentation workflow.
iQedaFetch LeetCode problem details and generate Rust templates in the problems/ directory.
brainbrewlabsPublishes documentation to GitHub Pages, Vercel, or Netlify from source docs and build outputs.
bigeasyfreemanAutomate linting and syntax checking before testing in TDD workflows.
pingqLINGuide developers to write self-explanatory code with minimal comments.
