chore: add .skillsaw.yaml to exclude vendored gws skills#41
Conversation
The gws skills are auto-generated from upstream via `gws generate-skills`. Exclude them from skillsaw linting to avoid content-rule violations on text we don't control, matching the existing markdownlint ignore pattern. Assisted-by: Claude:claude-opus-4-6
|
Caution Review failedPull request was closed or merged during review 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 (1)
📝 WalkthroughWalkthroughThe ChangesConfiguration Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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
.skillsaw.yamlconfig to excludegws/skills/**from skillsaw lintinggws generate-skills— content-rule violations on vendored text should be suppressed at the config level rather than by modifying the files (which creates drift).markdownlint-cli2.jsoncignore pattern for the same pathTest plan
uvx skillsaw --strictpasses with 0 errors, 0 warningsSummary by CodeRabbit