fix(docs): Use rule tag families in skills - #358
Open
misonijnik wants to merge 1 commit into
Open
Conversation
Give every custom library source/sink a role-family `tags` value, and document how a `tag:` ref expands to the language-scoped union of every active rule carrying it — built-in or custom — so several custom sources can share one project-specific family. Rework the assemble-lib-rules workflow around expanding the joins that already exist and adding only the combinations still uncovered, rather than writing one join per (vuln class, sink). Keep the create-rule test joins on exact `rule:` refs, since tag expansion would pull in every active family member and stop the test isolating the component under test. skills/ is regenerated from skills-templates/ via build.py; no engine, rule, or model behaviour changes.
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
1 participant
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.
No description provided.