sarj/reuse/vague-capability Use specific capability names
Reusable libraries avoid controlled generic capability names.
warning
Examples
capability = 'utils'capability = 'request-signing'Why it matters
Generic names become dependency magnets and conceal ownership.
How detection works
A reusable library uses common, core, helpers, shared, or utils as its capability.
What is inspected
- reusable component kind and capability
How to fix it
Name the stable capability rather than its generic utility role.
- Choose the cohesive public contract as the capability name.
Verify
- Run repo-lint again and confirm the rule passes.