@pablozrrrr/jevguard 0.2.2 → 0.3.0
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 +315 -95
- package/cli/main.js +4729 -1413
- package/index.js +4239 -1650
- package/package.json +6 -2
- package/skills/jev-init/SKILL.md +9 -3
- package/skills/jev-init/validate-init.js +2002 -696
- package/skills/jevguard-rules/SKILL.md +45 -3
- package/skills/jevguard-rules/validate-rules.js +1915 -613
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pablozrrrr/jevguard",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.3.0",
|
|
4
4
|
"description": "OpenCode plugin that reviews a completed agent turn against a repository semantic rule using Jev.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -23,7 +23,7 @@
|
|
|
23
23
|
],
|
|
24
24
|
"engines": {
|
|
25
25
|
"bun": ">=1.1.0",
|
|
26
|
-
"opencode": ">=
|
|
26
|
+
"opencode": ">=2.2.2 <2.3"
|
|
27
27
|
},
|
|
28
28
|
"repository": {
|
|
29
29
|
"type": "git",
|
|
@@ -51,5 +51,9 @@
|
|
|
51
51
|
"@napi-rs/keyring": "2.1.0",
|
|
52
52
|
"@typesafe-ai/sdk": "0.6.0",
|
|
53
53
|
"yaml": "2.9.1"
|
|
54
|
+
},
|
|
55
|
+
"peerDependencies": {
|
|
56
|
+
"@opencode/plugin": "2.2.2",
|
|
57
|
+
"effect": "4.0.6"
|
|
54
58
|
}
|
|
55
59
|
}
|
package/skills/jev-init/SKILL.md
CHANGED
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: jev-init
|
|
3
3
|
description: Use when a repository has no JevGuard policy yet and the user wants to bootstrap `.jev/rules.md` and `.jev/config.yaml` from explicit constraints and strong local evidence. Bounded, read-only inventory; stops if either file already exists; previews both files and requires explicit confirmation before writing. Do not use to edit an existing policy, for credentials, or to run a review.
|
|
4
4
|
license: MIT
|
|
5
|
-
compatibility: opencode >=
|
|
5
|
+
compatibility: opencode >=2.2.2 <2.3
|
|
6
6
|
---
|
|
7
7
|
|
|
8
8
|
# JevGuard init
|
|
@@ -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
|
|