Repository navigation
fix: CLI-only skills remain discoverable when project path casing differs - #1616
Merged
Merged
Conversation
Route both current-project and CLI-only source-root comparisons through one platform-aware seam while preserving the existing ordinal comparison. Passing the runtime platform explicitly keeps the upcoming path identity policy free of hidden environment dependencies.
Treat differently cased paths as identical for Windows and macOS editor sessions while retaining ordinal identity on Linux. This prevents the CLI-only source gate from dropping equivalent current-project paths on the default case-insensitive filesystems. Add a deterministic three-platform contract test. Per-volume filesystem probing is intentionally avoided because it would add I/O and complexity to a narrow source-discovery gate.
Contributor
📝 WalkthroughWalkthroughSkillSourceRootEnumerator's path comparison logic is refactored to use a new platform-aware HaveSamePathIdentityAtPlatform helper, applying case-insensitive comparison on Windows/macOS editors and case-sensitive comparison elsewhere. A new parameterized test validates this behavior across platforms. ChangesPlatform-aware path identity
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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 |
There was a problem hiding this comment.
All reported issues were addressed across 2 files
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
Path.GetFullPath preserves trailing directory separators, so equivalent project roots could still fail the centralized identity check. Normalize optional trailing separators while retaining filesystem roots such as slash and drive roots. Add three-platform regression coverage for trailing-separator equivalence.
Merged
RyanXie123
pushed a commit
to RyanXie123/unity-cli-loop
that referenced
this pull request
Sep 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
User Impact
Changes
Test Scope Note
Packages/srcis still enumerated later as a direct package root and rediscovers the sameEditor/CliOnlyTools~files. The attempted integration test passed before the fix and was removed because it did not constrain the faulty comparison.GetCliOnlySkillSourceRootandIsCliOnlySkillSourceRoot.Verification
SkillInstallLayoutTests: 19 passed.ToolSkillSynchronizerTests: 52 passed.git diff --check.Review Response
Path.GetFullPathpreserves the separator. The fix uses root-safe normalization rather than a plainTrimEndthat could collapse/or a drive root.Compatibility