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.
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.