feat: add --auto flag, redefine --quick as plan-only#130
feat: add --auto flag, redefine --quick as plan-only#130
Conversation
…--auto (full autonomous) paths
…pproval check to stop-watcher
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 16 minutes and 19 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
📝 WalkthroughWalkthroughThis PR introduces a new Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~28 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 4
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@plugins/ralph-speckit/commands/start.md`:
- Around line 168-176: The autonomous-mode flow needs to write the
.current-feature pointer before kicking off the first autonomous phase so
external guards/readers can resolve the active state; modify the Autonomous Mode
Routing logic to persist the current feature file (write .current-feature)
immediately when quickMode or autoMode is true and before delegating to the
first phase, ensuring this happens prior to where .specify/.current-feature is
currently written (so quick-mode-guard.sh and stop-watcher.sh can find the
active feature for their guards and stop-loop). Update the code path that
handles quickMode/autoMode to call the same routine that writes the
.current-feature pointer (or inline the write) before invoking the phase
delegation, and ensure the file format/path exactly matches what
quick-mode-guard.sh and stop-watcher.sh expect.
- Around line 181-188: The state persisted after tasks completion is incomplete
before branching for quickMode/autoMode: ensure you compute totalTasks (count
task checkboxes) and write the shared execution bootstrap fields into the state
file—set phase: "execution", taskIndex: 0, and totalTasks—before applying the
per-path changes (for quickMode also set awaitingApproval: true; for autoMode
proceed to implementation). Update the logic around the post-tasks fork (the
quick/auto branch in the start flow) so both paths call the same state-write
that includes phase, taskIndex and totalTasks to prevent stop-watcher.sh and
stop-hook resume from misbehaving.
In `@plugins/ralph-specum-codex/skills/ralph-specum-start/SKILL.md`:
- Around line 52-53: The awaitingApproval flow in SKILL.md (the `--quick` branch
described in the steps for "With `--quick`") must produce a visible reply that
conforms to the Codex approval contract: when you set `awaitingApproval: true`
(in the `--quick` path), update the instruction text to explicitly list the
generated artifacts (research, requirements, design, tasks), include a one- or
two-sentence summary for each, and end the user-facing message with exactly one
explicit choice prompt (e.g., "Approve plan and run implement" or "Request
changes")—ensure that exact prompt is the final line so the approval gate is
correctly applied.
In `@plugins/ralph-specum/commands/start.md`:
- Around line 261-262: Update the Step 5 summary in start.md to split behavior
by mode: clearly state that when invoked with --quick (or via
$ralph-specum-start quick mode) the flow stops after planning and does not
transition to execution or invoke spec-executor, whereas only --auto
(autonomous) continues into execution and calls spec-executor; locate the Step 5
summary text referencing "transitions to execution" and "invokes spec-executor"
and change it to explicitly describe the two branches (quick stops after
planning, auto proceeds to execution) and mention $ralph-specum-start usage for
create/resume/quick to avoid the old --quick-as-execute wording.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 108d5be4-c11c-4858-8cef-aef45fe7f3b5
📒 Files selected for processing (16)
.claude-plugin/marketplace.jsonplugins/ralph-speckit/.claude-plugin/plugin.jsonplugins/ralph-speckit/commands/start.mdplugins/ralph-speckit/hooks/scripts/quick-mode-guard.shplugins/ralph-speckit/hooks/scripts/stop-watcher.shplugins/ralph-specum-codex/skills/ralph-specum-start/SKILL.mdplugins/ralph-specum-codex/skills/ralph-specum/SKILL.mdplugins/ralph-specum/.claude-plugin/plugin.jsonplugins/ralph-specum/commands/start.mdplugins/ralph-specum/hooks/scripts/quick-mode-guard.shplugins/ralph-specum/hooks/scripts/stop-watcher.shplugins/ralph-specum/references/intent-classification.mdplugins/ralph-specum/references/quick-mode.mdplugins/ralph-specum/skills/smart-ralph/SKILL.mdspecs/add-auto-flag/.progress.mdspecs/add-auto-flag/tasks.md
Keep --quick/--auto flag split from this branch and main's non-negotiable STOP language for the no-flag case.
- speckit start.md: move .current-feature write before autonomous routing so guards can resolve active feature during autonomous phases - speckit start.md: compute totalTasks and set execution bootstrap fields (phase, taskIndex, totalTasks) before quick/auto branch - codex start SKILL.md: --quick path now lists artifacts and ends with explicit choice prompt per Codex approval contract - specum start.md: Step 5 summary distinguishes --quick (stops after planning) from --auto (continues to execution)
Summary
--quickas plan-only mode: runs all 4 planning phases autonomously (research, requirements, design, tasks) then stops before implementation--autoas full autonomous mode (what--quickpreviously did): runs all phases including implementation end-to-end--quickand--autoare mutually exclusive; combining them errors immediatelyMigration
Existing
--quickusers: replace with--autoto restore the old full-autonomous behavior.Files changed
ralph-specum (6 files): start.md, quick-mode.md, intent-classification.md, stop-watcher.sh, quick-mode-guard.sh, smart-ralph SKILL.md
ralph-speckit (4 files): start.md, stop-watcher.sh, quick-mode-guard.sh (new), plugin.json
ralph-specum-codex (2 files): ralph-specum-start/SKILL.md, ralph-specum/SKILL.md
Root: marketplace.json + plugin.json version bumps (ralph-specum 4.10.0, ralph-speckit 0.5.3)
Summary by CodeRabbit
New Features
--autoflag for full end-to-end autonomous workflow--quickflag to planning-only mode that stops before implementation--quickand--autoflags are mutually exclusiveChores