@kirill.konshin/lint 0.6.6 → 0.6.8
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 +1 -1
- package/package.json +1 -1
- package/rules/github.md +3 -1
- package/rules/gitlab.md +2 -5
- package/rules/nx.md +1 -0
- package/skills/lint-github/SKILL.md +214 -42
- package/skills/lint-gitlab/SKILL.md +24 -0
- package/skills/spec-tools/SKILL.md +1 -1
- package/skills/spec-tools/references/contract.md +34 -10
- package/skills/spec-tools/references/gitlab.md +4 -3
- package/skills/spec-tools/references/rules/common.md +20 -10
- package/skills/spec-tools/references/rules/spec-verify-judge.md +9 -8
- package/skills/spec-tools/references/rules/spec-verify.md +7 -3
- package/skills/spec-tools/scripts/cli.js +418 -257
- package/skills/spec-verify/SKILL.md +10 -10
|
@@ -24,11 +24,11 @@ Do not compare code with code.
|
|
|
24
24
|
## Contradictory rules
|
|
25
25
|
|
|
26
26
|
- Two requirements conflict when one system cannot obey both.
|
|
27
|
-
- A conflict is a defect in the specification.
|
|
27
|
+
- A conflict is a defect in the specification. Its severity is in the WARN band or lower. The owner decides.
|
|
28
28
|
|
|
29
29
|
## A rule redundant with, or substantially overlapping, another
|
|
30
30
|
|
|
31
|
-
- Two requirements that state the same rule are `spec-dup`.
|
|
31
|
+
- Two requirements that state the same rule are `spec-dup`. Its severity is always in the INFO band.
|
|
32
32
|
|
|
33
33
|
## A rule that no longer matches the implementation or architecture
|
|
34
34
|
|
|
@@ -41,10 +41,14 @@ Do not compare code with code.
|
|
|
41
41
|
## A rule whose tests satisfy the wording while failing to protect the intent
|
|
42
42
|
|
|
43
43
|
- For each test that a scenario binds, make sure that the test asserts the outcome of the scenario. The name of the test is not evidence.
|
|
44
|
-
- A test that asserts less than its scenario is `untested`.
|
|
44
|
+
- A test that asserts less than its scenario is `untested`. Its severity is always in the INFO band.
|
|
45
45
|
|
|
46
46
|
## Coverage
|
|
47
47
|
|
|
48
48
|
- A check is full when you judged each item that the part lists for it, and each requirement id is in your judged list.
|
|
49
49
|
- A check is sampled only when an assigned source was not available after you tried to read it. Name that source.
|
|
50
50
|
- An uncertain conclusion is a finding with a low `readerConfidence`. It is not sampled coverage.
|
|
51
|
+
|
|
52
|
+
## The numbers
|
|
53
|
+
|
|
54
|
+
- Write the severity as `readerSeverity` and the confidence as `readerConfidence`.
|