Conversation
The assertion now matches "subagent-driven-development", "Subagent-Driven Development", and "Subagent Driven" since Claude's responses may use different casing and formatting styles. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add Test 8 to verify that using-git-worktrees is mentioned as a required skill for subagent-driven-development. This test will initially fail per TDD approach - the skill file needs to be updated to pass this test. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
TDD: Test verifies that subagent-driven-development skill warns against starting implementation directly on main/master branch. Test expects skill to recommend worktree or feature branch instead. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…d skill Adds using-git-worktrees as the first required workflow skill in the Integration section. This makes explicit that an isolated workspace should be set up before starting subagent-driven development. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
…list Add explicit warning against starting implementation on main/master branch without first using a worktree for isolation. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Update Integration section to show bidirectional relationship: subagent-driven-development and executing-plans now list using-git-worktrees as required, so this skill should list them as callers. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add Integration section referencing using-git-worktrees skill as required, consistent with subagent-driven-development skill. Also add reminder to never start on main/master branch. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Instead of prohibiting main branch work entirely, allow it with explicit user consent. This is more flexible while still ensuring users are aware of the implications. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
📝 WalkthroughWalkthroughUpdates to workflow skill documentation and tests establish explicit prerequisites for git worktree setup and enforce safeguards against starting implementation on main/master branches without user consent. Changes span three skill definitions and related test validations. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related issues
Possibly related PRs
Suggested reviewers
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)
Tip 🧪 Unit Test Generation v2 is now available!We have significantly improved our unit test generation capabilities. To enable: Add this to your reviews:
finishing_touches:
unit_tests:
enabled: trueTry it out by using the Have feedback? Share your thoughts on our Discord thread! 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 |
|
Thanks! merged |
…ream) - Add red flag: never start on main/master without explicit user consent - Make using-git-worktrees REQUIRED before subagent-driven-development - Make using-git-worktrees REQUIRED before executing-plans - Update integration sections with cross-references Cherry-picked from upstream PRs obra#382, obra#361
Summary
using-git-worktreesas a required prerequisite forsubagent-driven-developmentandexecuting-plansskillsusing-git-worktreesto list these skills as callersProblem
The
subagent-driven-developmentandexecuting-plansskills execute implementation plans but don't require setting up an isolated workspace first. This leads to implementations being committed directly tomain/master, which:finishing-a-development-branchto fail (nothing to merge/PR)Solution
using-git-worktreesa required prerequisite in both skillsFiles Changed
skills/subagent-driven-development/SKILL.mdskills/executing-plans/SKILL.mdskills/using-git-worktrees/SKILL.mdtests/claude-code/test-subagent-driven-development.shTest Plan
🤖 Generated with Claude Code
Summary by CodeRabbit
Release Notes
Documentation
Tests
✏️ Tip: You can customize this high-level summary in your review settings.