fix(gws): correct skillsaw content violations via skillsaw fix --llm#40
fix(gws): correct skillsaw content violations via skillsaw fix --llm#40stbenjam wants to merge 2 commits into
Conversation
Remove phrasing that triggered skillsaw content checks ("Note that",
"i.e.") and clarify Ctrl-C behavior in gws-gmail-watch.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
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 ignored due to path filters (3)
📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe pull request updates the version field in ChangesPlugin Version Management
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
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 |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
There was a problem hiding this comment.
This was to get it below the 3000 "warn" limit for a skill's token budget. You could also disable this check, turn off --strict or move to progressive discovery in a references/ folder/
Remove phrasing that triggered skillsaw content checks. As you don't have a
.skillsaw.yaml(skillsaw init) you'll automatically get new rules. I try my best to avoid breaking anything but new rules obviously could fire.This fixes the content rules that fire on the latest (
skillsaw fix --llm)Summary by CodeRabbit