skills.rest
Skro11X
Skro11XCOMMUNITY
Explore all skills by this author →
GitHub

aif-verify

Validate code implementations against project plans for build, test, lint, and dependency integrity.

Updated Mar 13, 2026
Search Tags:#code quality#testing#ci/cd#verification#auditing#plan adherence
One-click install
npx skills add https://github.com/Skro11X/all_vibe_code_test --skill aif-verify-skro11x
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: aif-verify
Source: https://github.com/Skro11X/all_vibe_code_test/tree/main/.claude/skills/aif-verify
Command: npx skills add https://github.com/Skro11X/all_vibe_code_test --skill aif-verify-skro11x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guarantees that implemented code precisely matches the project plan, meets quality standards, and is ready for production, preventing costly errors and rework.

Core Features & Use Cases

  • Task Completion Audit: Verifies every requirement of each task in the plan has been implemented.
  • Code Quality Checks: Assesses build status, test results, linting, and dependency integrity.
  • Consistency Verification: Detects drift between the plan and code, checks for leftover artifacts, and ensures configuration is documented.
  • Use Case: After a developer completes a new feature, run this Skill to automatically confirm all planned user stories are coded, tests pass, and no technical debt like 'TODO' comments were left behind.

Quick Start

Use the aif-verify skill to check the implementation against the last plan.

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 project plan?▼

To verify code matches a project plan, validate completed implementations against planned tasks to ensure all requirements are addressed and quality standards are met before merging.

What is plan-code drift and how do I detect it?▼

Plan-code drift occurs when the implemented code diverges from the original project plan. Detect drift and identify leftover artifacts by running consistency verification checks against the plan.

How to check for leftover artifacts and TODO comments before merging code?▼

Check for leftover artifacts and TODO comments by running a consistency verification audit that scans the implementation for technical debt, linting compliance, and undocumented configurations.

Can I enforce strict test coverage and linting compliance for pre-merge quality assurance?▼

Yes, you can enforce pre-merge quality assurance by operating in strict mode to validate build success, test coverage, linting compliance, and dependency integrity against required standards.

Does project plan verification work for auditing dependency integrity?▼

Yes, project plan verification includes code quality checks that assess dependency integrity alongside build status, test results, and linting compliance to ensure production readiness.

What is the difference between normal and strict verification modes?▼

Normal and strict verification modes differ in enforcement severity, with strict mode applying rigorous pre-merge quality assurance checks for plan adherence, test coverage, and linting compliance.

Related Skills

Explore More Software Engineering Skills→
Lin117-shygoLin117-shygo

update-spec

Refresh executable code-spec contracts and documentation after completing a task.

Community
Intermediate
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
protofireprotofire
3

protofire-qa-agent

Audit smart contracts with Slither, Echidna, and Foundry fuzz testing.

Official
Advanced
Objective-ArtsObjective-Arts

qodana-scan

Run read-only Qodana static analysis to detect code issues.

Official
Intermediate