fix: use generic progress tracking in prompts#1180
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis PR replaces references to the deprecated TodoWrite tool with instructions to use the agent's native planning/checklist mechanism across workflow templates. The ff-change and propose skill/command templates are updated with new progress-tracking guidance, test baselines are refreshed, and a new validation test ensures the templates contain the new mechanism and exclude TodoWrite references. ChangesTodoWrite Tool Replacement in Workflow Templates
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 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 |
Summary
Why
The generated fast-forward/propose prompts can reference a tool that is not available in some Claude Code environments. The workflow only needs progress tracking, so generic wording is enough and works across adapters.
Fixes #643.
Validation
Summary by CodeRabbit
Release Notes