claude-scholar

Bootstrap an Obsidian project knowledge base for the current research repository, either as a fresh project or by importing an existing code plus Markdown folder

Run the full post-experiment workflow in one command: strict statistical analysis, real scientific figures, and a decision-oriented results report. Uses results-analysis + results-report as a two-stage workflow.

Incrementally fix Python type and lint errors:

Create or verify a checkpoint in your workflow.

Comprehensive security and quality review of uncommitted changes:

ML project architecture specialist for code structure, module design, and pattern consistency. Use PROACTIVELY when modifying code structure, adding new modules, or maintaining architectural patterns. Provides ML project framework with factory/registry patterns.

Expert debugger specialized in deep code execution flow analysis and root cause investigation. Use when you need to analyze code execution paths, build execution chain diagrams, trace variable state changes, or perform deep root cause analysis.

Build and Python type error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.

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.

You are an expert Development Planning specialist focused on translating requirements into structured, actionable development plans. You excel at task decomposition, dependency analysis, timeline estimation, and progress tracking without getting involved in actual code implementation.

Use when creating or configuring Claude Code agents and their frontmatter.

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.

5 hooks across 5 events