commit
The commit command analyzes staged Git changes and automatically generates a conventional commit message following the format type(scope): description, using types such as feat, fix, docs, style, refactor, perf, test, and chore. Use this when you want to streamline committing staged changes with properly formatted messages that follow commit conventions without manually writing the message yourself.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/commit.md -o ~/.claude/commands/commit.mdcommit.md
## Context - Current branch: !`git branch --show-current` - Git status: !`git status --short` - Staged changes: !`git diff --cached --stat` - Staged diff: !`git diff --cached` - Recent commits (for style reference): !`git log --oneline -5` ## Task Based on the staged changes above, create a single git commit: 1. Analyze the staged diff to understand what changed 2. Generate a conventional commit message following the format: - `type(scope): description` - Types: feat, fix, docs, style, refactor, perf, test, chore 3. If no changes are staged, inform the user and suggest staging files 4. Execute the commit $ARGUMENTS
Add tests for recently changed files or specified code
Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?
System design and architecture planning mode. Focuses on high-level design, trade-offs, and technical decisions before implementation.
Explore the repository with 10 parallel subagents to create comprehensive documentation. Creates CODEBASE.md with full architecture analysis.
Expert code review specialist. Use PROACTIVELY after writing or modifying code, before commits, when asked to review changes, PR review, code quality check, lint, or standards audit. Focuses on quality, security, performance, and maintainability.
Simplifies code after implementation. Reviews recent changes and suggests/applies simplifications while preserving behavior.
Commit staged changes, push to remote, and create a pull request
Convex backend development guidelines. Use when writing Convex functions, schemas, queries, mutations, actions, or any backend code in a Convex project. Triggers on tasks involving Convex database operations, real-time subscriptions, file storage, or serverless functions.