kb-literature-review
The kb-literature-review command executes a structured literature synthesis workflow that transforms source paper notes into organized knowledge artifacts and writing drafts. Use it to synthesize research papers into literature overviews, method taxonomies, research gaps, and related-work sections, with conditional outputs based on whether source notes contain sufficient evidence records to support claims.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/kb-literature-review.md -o ~/.claude/commands/kb-literature-review.mdkb-literature-review.md
# /kb-literature-review Use `obsidian-literature-workflow`. Conditional outputs: - `Knowledge/Literature Overview.md` only when paper notes contain enough Evidence Records for synthesis - `Knowledge/Method Taxonomy.md` when useful and evidence-backed - `Knowledge/Research Gaps.md` when useful and evidence-backed - `Knowledge/Claim Map.md` or a warning when evidence is weak - `Writing/related-work-draft.md` only when promoted claims pass the evidence gate - `Maps/literature.canvas` Keep source notes in `Sources/Papers/`. Do not turn source notes into synthesis notes. Evidence gate: - refuse polished `Knowledge` or `Writing` synthesis when paper notes lack Evidence Records, - keep abstract-only or webpage-placeholder items in coverage / `To-Read`, - generate a warning or `Knowledge/Claim Map.md` instead of a mature related-work draft when evidence is weak, - preserve claim strength on literature canvas edges.
Use when creating or configuring Claude Code agents and their frontmatter.
Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem", "something is broken", "this isn't working", "why is this failing", or reports errors/exceptions/bugs. Provides systematic debugging workflow and common error patterns.
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or improve how a team performs code review.
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.