quick-fix
The quick-fix command automatically detects your project type (Node.js, Python, or Go) and identifies linting, type, and syntax errors using appropriate tools like TypeScript, ESLint, and Ruff. It applies minimal fixes to resolve the specified issues, then re-runs validation checks to confirm corrections. Use this command when you need rapid resolution of straightforward errors without manual debugging.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/HEAD/commands/quick-fix.md -o ~/.claude/commands/quick-fix.mdquick-fix.md
## Context - Package manager detection: !`ls package.json 2>/dev/null && echo "Node.js project" || ls requirements.txt pyproject.toml 2>/dev/null && echo "Python project" || ls go.mod 2>/dev/null && echo "Go project" || echo "Unknown"` - Recent changes: !`git diff --name-only HEAD~1 2>/dev/null || git diff --name-only` - TypeScript errors (if applicable): !`npx tsc --noEmit 2>&1 | head -30 || echo "No TypeScript"` - ESLint errors (if applicable): !`npx eslint . --format compact 2>&1 | head -30 || echo "No ESLint"` - Python lint (if applicable): !`python3 -m ruff check . 2>&1 | head -30 || python3 -m flake8 . 2>&1 | head -30 || echo "No Python linter"` ## Task Fix the issue described below: 1. Identify the type of error (type error, lint, syntax, logic) 2. Locate the problematic file(s) 3. Apply the minimal fix needed 4. Verify the fix by re-running the relevant check 5. Report what was fixed Target: $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.
Create a conventional commit with auto-generated message
Commit staged changes, push to remote, and create a pull request