commit
This command stages and commits local Git changes using the Conventional Commits format, which standardizes commit messages with a type prefix (feat, fix, docs, style, refactor, perf, test, chore) and optional scope. Use it when ready to create a formatted commit of your work before pushing to a remote repository, ensuring clear project history and compatibility with automated tools.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/Galaxy-Dawn/claude-scholar/HEAD/commands/commit.md -o ~/.claude/commands/commit.mdcommit.md
# Commit Stage and commit changes using Conventional Commits format. ## Instructions 1. **Check Git Status** - Run `git status` to review all changes - Run `git diff` to inspect modifications 2. **Analyze Changes** - Review changed files and their content - Determine commit type and scope - Draft a concise commit message 3. **Commit Type Reference** ``` feat - New feature fix - Bug fix docs - Documentation only style - Code style (formatting, semicolons, etc.) refactor - Code refactoring (no feature/fix) perf - Performance improvement test - Adding or updating tests chore - Build, CI, tooling, dependencies ``` 4. **Commit Message Format** ``` <type>(<scope>): <subject> <body> ``` - Subject: imperative mood, no period, max 72 chars - Body: explain what and why (optional for small changes) - Scope: affected module (data, model, config, trainer, utils, workflow) 5. **Stage and Commit** - Stage relevant files with `git add` - Do NOT stage files containing secrets (.env, credentials, tokens) - Create commit with formatted message - Do not include `Co-Authored-By` footers unless the user explicitly asks for them - Verify with `git log --oneline -1` ## Notes - This command only commits locally. Use `/update-github` to also push. - Always confirm the commit message with the user before committing. - If unsure about type or scope, ask the user.
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.
Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples:
Use this agent when the user asks to "conduct literature review", "search for papers", "analyze research papers", "identify research gaps", "review related work", or mentions starting a research project. This agent integrates with Zotero for automated paper collection, organization, and full-text analysis. Examples:
Use this agent when the user provides a research paper (PDF/DOCX/arXiv link) or asks to learn writing patterns from papers, extract venue-specific writing signals, study paper structure, or mine rebuttal strategies. The agent writes extracted knowledge into the active installed paper-miner writing memory for ml-paper-writing. It does not maintain project-specific writing memory.
Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.
Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.
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.
Create a new project from template with uv and Git initialization