From claude-commands
Executes a sequential code review workflow: /cons for bug and correctness checks, /pushl, /reviewdeep, /copilot, and /guidelines.
npx claudepluginhub jleechanorg/claude-commandscommands/## β‘ EXECUTION INSTRUCTIONS FOR CLAUDE **When this command is invoked, YOU (Claude) must execute these steps immediately:** **This is NOT documentation - these are COMMANDS to execute right now.** **Use TodoWrite to track progress through multi-phase workflows.** ## π¨ EXECUTION WORKFLOW ### Phase 1: Execute Documented Workflow **Action Steps:** 1. Review the reference documentation below and execute the detailed steps sequentially. ## π REFERENCE DOCUMENTATION # /auto Command Run the following workflow in order, making sure to complete each command fully without skipping any steps: ...
/autoAnalyzes natural language query to detect development intent and routes to optimal Claude Octopus workflow like debug, TDD, or research.
/autoAutomates full dev pipeline from planning/tests/review/verify to commit/PR/docs-sync for feature/bugfix/refactor tasks. Requires task desc; optional --mode flag.
/autoAnalyzes task and auto-executes optimal strategy: direct execution, hybrid PRD generation, worktree development, or mega-plan orchestration. Supports --flow quick/standard/full.
/autoActivates autonomous PLAN-ACT-EVAL iteration cycle using TDD workflow until zero critical/high issues achieved, then outputs success summary or suggestions.
/autoAutomates full development lifecycle from requirements to production-ready code including planning, implementation, testing, debugging, validation, and optional release.
/autoOrchestrates full code review pipeline on feature branch: generates design intent, quality criteria, PR body, auto-reviews changes, applies fixes, produces artifacts in .review-artifacts/.
When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.
Action Steps:
Run the following workflow in order, making sure to complete each command fully without skipping any steps:
/cons β Carefully review the code for bugs and correctness issues, including logic errors, edge cases, off-by-one errors, and violations of expected behavior. Focus only on correctness, not style or performance. For more details on the /cons command and examples of issues to look for, see the Cons Command Documentation./pushl/reviewdeep/copilot/guidelines