@pablozrrrr/jevguard 0.2.2 → 0.2.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +75 -16
- package/cli/main.js +951 -70
- package/index.js +877 -73
- package/package.json +1 -1
- package/skills/jev-init/SKILL.md +8 -2
- package/skills/jev-init/validate-init.js +528 -65
- package/skills/jevguard-rules/SKILL.md +44 -2
- package/skills/jevguard-rules/validate-rules.js +528 -65
package/package.json
CHANGED
package/skills/jev-init/SKILL.md
CHANGED
|
@@ -101,8 +101,14 @@ A single README sentence, an isolated code sample, personal preference, or an
|
|
|
101
101
|
aspiration the repository does not already follow is **not** strong evidence. Exclude
|
|
102
102
|
speculative rules and say which candidates you dropped and why.
|
|
103
103
|
|
|
104
|
-
Each rule block keeps the document grammar
|
|
105
|
-
|
|
104
|
+
Each rule block keeps the document grammar. The accepted metadata is `severity`,
|
|
105
|
+
repeatable `scope` (a leading `!` excludes), and optional `evidence` (`code`, the
|
|
106
|
+
default, `docs`, or `any`). Provenance is **never** written inside a rule block.
|
|
107
|
+
|
|
108
|
+
Prefer a bounded `scope:` over a repository-wide rule: a convention that only holds under
|
|
109
|
+
particular paths must say so, or it will fire where it does not apply. Add
|
|
110
|
+
`evidence: docs` or `evidence: any` only when the rule genuinely inspects documentation,
|
|
111
|
+
because the default `code` class excludes prose.
|
|
106
112
|
|
|
107
113
|
### 5. Write the provenance preamble before the rules
|
|
108
114
|
|