aif-verify

Verify software implementations against project plans and architectural constraints.

Updated Jul 15, 2026

Search Tags:#automation #testing #quality assurance #code review #verification #compliance

Ready to run

npx skills add https://github.com/o2b3k/idomarketingbot --skill aif-verify-o2b3k

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/o2b3k/idomarketingbot/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/o2b3k/idomarketingbot --skill aif-verify-o2b3k

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill prevents deployment of incomplete or buggy code by systematically verifying that all planned tasks were executed, quality standards are met, and no technical debt or configuration drift was introduced.

Core Features & Use Cases

Task Audit: Automatically cross-references implemented code against the original plan to ensure 100% completion.
Quality Gates: Validates build integrity, test coverage, and linting status across changed files.
Context Synchronization: Detects drift between the codebase and project documentation like architecture, roadmap, and rules.
Use Case: After finishing a feature branch, run this skill to generate a comprehensive verification report that confirms all requirements are satisfied and the code is ready for merge.

Quick Start

Run the aif-verify skill to perform a standard quality check on the current branch implementation.

Frequently Asked Questions about aif-verify

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

FAQPage Schema

How do I verify code implementation against project plans before merging?▼

To verify code implementation against project plans, you can automatically cross-reference completed tasks with the original architectural constraints to ensure 100% completion and prevent deploying incomplete features.

What is configuration drift detection in software quality assurance?▼

Configuration drift detection identifies inconsistencies between your codebase and project documentation, ensuring that architecture, roadmap, and rules remain synchronized and production-ready throughout development.

How do I enforce strict quality gates for build stability and test coverage?▼

Enforcing strict quality gates involves validating build integrity, evaluating test results, and checking linting status across changed files to confirm that quality standards are met before merge.

Does automated task audit work for feature branch verification?▼

Yes, automated task audit works for feature branch verification by cross-referencing implemented code against the original plan to generate a comprehensive verification report confirming all requirements are satisfied.

What are the limitations of automated code review for technical debt identification?▼

Automated code review identifies technical debt and configuration drift, but limitations include relying on existing project documentation accuracy and requiring defined architectural constraints to properly evaluate task fulfillment.

Why does my code fail quality checks despite passing local tests?▼

Code may fail quality checks due to configuration drift, incomplete task fulfillment against the original plan, or documentation inconsistencies that violate strict quality gates enforced during repository evaluation.