aif-verify

Verify completed implementations against plans for task coverage and quality.

Updated Aug 4, 2025
One-click install
npx skills add https://github.com/Svarog83/php-log-monitor --skill aif-verify-svarog83
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/Svarog83/php-log-monitor/tree/main/.cursor/skills/aif-verify
Command: npx skills add https://github.com/Svarog83/php-log-monitor --skill aif-verify-svarog83

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verify completed implementation against the plan. Checks that all tasks were fully implemented, nothing was forgotten, code compiles, tests pass, and quality standards are met.

Core Features & Use Cases

  • Plan-to-implementation audit and validation
  • Build, test, and lint verification
  • Documentation and repository alignment checks
  • Use Case: run after /aif-implement to ensure readiness for review or deployment.

Quick Start

Run the verification after a feature is implemented to ensure all tasks are complete and compliant.

Frequently Asked Questions about aif-verify

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

FAQPage Schema
How do I verify completed code matches the original implementation plan?

Run a plan-to-implementation audit on feature branches to verify task completeness, check code compilation, validate test results, and ensure alignment with the original plan.

Can I automatically check if all planned tasks were fully implemented before a pull request?

Yes, you can automatically audit pull requests to ensure all planned tasks were fully implemented, checking task coverage, lint status, and documentation alignment before review or deployment.

What does a plan-to-implementation code quality audit include?

A plan-to-implementation code quality audit includes checking task completeness, code compilation, test results, lint status, and alignment with the plan and description.

When do I need to run a feature branch verification check?

You need to run a feature branch verification check after feature implementation is complete to ensure all tasks are fully implemented, nothing is forgotten, and quality standards are met for review or deployment.

Does the verification audit check build, test, and lint status together?

Yes, the verification audit checks build, test, and lint status together, applying automated audits to task coverage, code compilation, test results, and documentation alignment on feature branches.

What are the limitations of automated plan-to-implementation compliance checks?

Automated plan-to-implementation compliance checks are limited to auditing task coverage, build status, test results, and lint status against existing plans, requiring completed code, tests, and documentation to function properly.