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.
Best use case
inspequte-rule-verify is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using inspequte-rule-verify should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/inspequte-rule-verify/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How inspequte-rule-verify Compares
| Feature / Agent | inspequte-rule-verify | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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: 1. `## Spec compliance findings` 2. `## FP/noise risks` 3. `## Determinism/stability risks` 4. `## Performance and regression concerns` 5. `## Recommendation (Go/No-Go)` - Save the same report to `verify-input/verify-report.md`. ## Minimal Context Loading 1. Read only files under `verify-input/`. 2. 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.
Related Skills
jwt-verify
Implement JWT verification middleware in FastAPI for user auth. Use when securing APIs or handling tokens.
Configure Firebase admin-only write rules
Guide to create an admin user in Firebase and set security rules so only admins can write to a collection while all users can read and register.
audit-rules
Audit Claude Code rule files for quality and compliance. Use when creating or validating .claude/rules/*.md files, or troubleshooting rule loading issues.
vueuse-library-rule
Encourages leveraging VueUse functions throughout the project to enhance reactivity and performance.
vue-3-nuxt-3-development-cursorrules-prompt-file-cursorrules
Apply for vue-3-nuxt-3-development-cursorrules-prompt-file. --- description: Applies to Vue 3 and Nuxt 3 projects, enforcing best practices for frontend development including TypeScript, TailwindCSS, and Composition API. globs: **/*.{vue,ts,js,jsx,tsx}
tailwind-css-nextjs-guide-cursorrules-prompt-file-cursorrules
Apply for tailwind-css-nextjs-guide-cursorrules-prompt-file. Prompt Generation Rules: - Analyze the component requirements thoroughly - Include specific DaisyUI component suggestions
starknet-react-rules
Specific rules for Starknet React projects, focusing on blockchain integration.
nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file-cursorrules
Apply for nextjs15-react19-vercelai-tailwind-cursorrules-prompt-file. --- description: Best practices for using Tailwind CSS in Next.js 15 and React 19 applications, including responsive design, custom configurations, and performance optimization. globs: app/**/*
html-tailwind-css-and-javascript-expert-rule
Sets the AI to act as an expert in HTML, Tailwind CSS, and vanilla JavaScript, focusing on clarity and readability for all HTML, JS, and CSS files.
html-specific-rules
Rules specific to HTML files, focusing on accessibility and Tailwind styling.
Creating Cursor Rules
Expert guidance for creating effective Cursor IDE rules with best practices, patterns, and examples
browser-api-usage-rules
Rules for effectively utilizing Chrome's browser APIs, including error handling and scheduling tasks.