inspequte-rule-verify

Verifies inspequte rule changes against provided evidence and generates a Go/No-Go recommendation report.

8|2|Updated Jan 12, 2026

Search Tags:#code quality #testing #static analysis #CI/CD #inspequte #rule verification

Ready to run

npx skills add https://github.com/KengoTODA/inspequte --skill inspequte-rule-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inspequte-rule-verify
Source: https://github.com/KengoTODA/inspequte/tree/main/.codex/skills/inspequte-rule-verify
Command: npx skills add https://github.com/KengoTODA/inspequte --skill inspequte-rule-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the verification of changes made to inspequte rules, ensuring compliance and identifying potential issues before they are merged.

Core Features & Use Cases

Isolated Verification: Verifies rule changes using only provided input files (spec.md, diff.patch, reports) without relying on external context like plan.md or chat logs.
Risk Assessment: Identifies findings related to spec compliance, false positives, determinism, and performance regressions.
Use Case: After implementing a new static analysis rule, use this Skill to generate a comprehensive verification report that includes a clear Go/No-Go recommendation based on the provided test results and code changes.

Quick Start

Run the inspequte-rule-verify skill using the contents of the verify-input directory.

Frequently Asked Questions about inspequte-rule-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify static analysis rule changes without external context?▼

Verify static analysis rule changes by placing spec.md, diff.patch, and reports into a verify-input directory to generate an isolated Go/No-Go recommendation report.

What issues are identified during static analysis rule verification?▼

Rule verification identifies spec compliance failures, false positive risks, determinism issues, and performance regressions based on the provided test evidence.

How do I assess false positive risks for new CI/CD rules?▼

Assess false positive risks by running isolated verification against provided evidence files, analyzing results to ensure accurate code quality checks before merging.

Does rule verification rely on chat logs or planning documents?▼

Rule verification does not rely on chat logs or planning documents; it strictly uses file-based evidence from a verify-input directory to ensure isolated determinism.

What is the best way to generate a Go/No-Go report for code quality rules?▼

Generate a Go/No-Go report by running isolated file-based verification against provided test results and code diffs to assess compliance and performance regressions.