Awesome-omni-skill inspequte-rule-verify

Perform isolated, file-based verification of an inspequte rule change using verify-input/. Use when producing a go/no-go verification report from spec.md, patch/diff, and report files without reading plan.md or chat logs.

install

source · Clone the upstream repo

git clone https://github.com/diegosouzapw/awesome-omni-skill

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/testing-security/inspequte-rule-verify" ~/.claude/skills/diegosouzapw-awesome-omni-skill-inspequte-rule-verify && rm -rf "$T"

manifest: skills/testing-security/inspequte-rule-verify/SKILL.md

source content

inspequte rule verify

Required Input Directory

```
verify-input/
```

Required files:

```
verify-input/spec.md
```
```
verify-input/diff.patch
```
(or equivalent change set)
```
verify-input/reports/*
```
(test/build/audit evidence)

Optional but recommended:

```
verify-input/changes/*
```
```
verify-input/changed-files.txt
```

Isolation Policy

Verify must only use
```
spec.md
```
, change set (
```
diff.patch
```
), and report files.
Do not read
```
src/rules/<rule-id>/plan.md
```
.
Do not use implementation discussion logs, chat context, or author intent.
If required input files are missing, fail with a clear blocked report.

Output

Print a verification report with these sections:

```
## Spec compliance findings
```
```
## FP/noise risks
```
```
## Determinism/stability risks
```
```
## Performance and regression concerns
```
```
## Recommendation (Go/No-Go)
```

Save the same report to
```
verify-input/verify-report.md
```
.

Minimal Context Loading

Read only files under
```
verify-input/
```
.
Avoid reading the broader repository unless a missing required file blocks verification.

Definition of Done

All required sections are present.
Every finding cites concrete evidence from files inside
```
verify-input/
```
.
Recommendation is explicit:
```
Go
```
or
```
No-Go
```
.
Report does not reference
```
plan.md
```
or discussion history.
Report calls out deviations from policy, including any
```
@Suppress
```
suppression behavior or non-JSpecify annotation semantics introduced without an explicit spec change.