solve-analyzelisted

Use when the user pastes their own solve() code and asks "分析一下我的代码", "帮我看看哪里错了", "对比一下", "review my solve", "check my code", "看看我的解法", "为什么WA", "为什么超时", "解法对比", "代码诊断". Also use when the user shares a completed solve() and wants a structured comparison against the standard template solution, root cause diagnosis, and automatic feedback to mistake_log / user_profile / exam-memory. This skill sits between solve-skeleton and algo-annotation in the pipeline: it diagnoses what went wrong, not how to annotate or how to build a skeleton. Handles both WA/TLE (full diagnosis) and AC code (lightweight style check).
Tenstu/Pass-LLM-with-LLM · ★ 4 · AI & Automation · score 77

Install: claude install-skill Tenstu/Pass-LLM-with-LLM

# Solve Analyze Skill Structured diagnosis layer that compares a user's solve() against a standard solution generated by the solve-skeleton pipeline. Produces a side-by-side diff report, identifies root cause tags, and triggers feedback loops into mistake_log, user_profile, and exam-memory MCP. This skill does not teach and does not build skeletons -- it diagnoses "what you wrote vs what you should have written." ## 1. Overview ### Pipeline Position ``` solve-skeleton (template) -> user fills logic -> ** solve-analyze (diagnosis) ** <-- this skill -> algo-annotation (# [防错] markers) -> mistake_log (error record) -> user_profile (weakness tracking) -> choice-q-create (targeted question generation) ``` ### Purpose When a user completes a solve() function and wants to know what went wrong, this skill: 1. Performs a quick triage to determine report depth (full diagnosis vs lightweight style check). 2. Statically analyzes the user's code for logic errors, anti-patterns, and suspicious lines. 3. Generates a reference solution via the solve-skeleton pipeline. 4. Produces a structured comparison report highlighting every meaningful difference. 5. Extracts root cause tags and feeds them back into the harness feedback loops. The output is actionable: each identified issue maps to a specific root cause tag, a suggested fix, and an automatic (or user-confirmed) write to the error tracking system. ### What This Skill Does NOT Do - Does not provide