Conversation
Root cause of eval failure: init-project.js --name=X always creates a subdirectory. When /setup runs in an empty directory, the project should be scaffolded in-place. --in-place uses the name for package.json but stays in cwd. SKILL.md now defaults to --in-place unless user explicitly requests a new subdirectory. https://claude.ai/code/session_01Hbxy31TkbujzukGFSxLcPw
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughA new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 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
Root cause of setup eval failures:
init-project.js --name=myappalways creates amyapp/subdirectory, but the grader checks the temp dir root.--in-placeflag: uses the name for package.json but scaffolds in the current directory--in-placeunless the user explicitly requests a new subdirectory--in-placebehavior (114 total)Test plan
npx jest --config '{}' tests/scripts/init-project.test.js— 15 tests pass--in-placecreates files in cwd, not in subdirectory--in-placeuses--namevalue in package.jsonhttps://claude.ai/code/session_01Hbxy31TkbujzukGFSxLcPw
Summary by CodeRabbit
Release Notes
New Features
--in-placeflag to scaffold projects directly in the current directory without creating a subdirectory.Documentation
--in-placeas the default option when the current directory is empty.Tests
--in-placeflag functionality and project naming behavior.