dx-step-verify

Coordinate a six-phase verification pipeline for code changes across compile, lint, test, secret scan, architecture, and code review.

6|3|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-step-verify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dx-step-verify
Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-step-verify
Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-step-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end verification of code changes by enforcing a 6-phase gate (compile, lint, test, secret scan, architecture, and code review with auto-fix). Only changes that pass all phases are allowed through.

Core Features & Use Cases

  • 6-phase verification pipeline that runs automatically on code changes.
  • Auto-fix loop with up to three cycles during the code-review phase to resolve issues without manual intervention.
  • Secret scanning and architecture checks to prevent credential leakage and architectural regressions.
  • Deterministic gating in CI/CD and PR workflows, ensuring consistent quality across teams.

Quick Start

Run after a successful /dx-step-build to automatically verify changes and auto-fix issues before opening a PR.

Frequently Asked Questions about dx-step-verify

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

FAQPage Schema
How do I automate code verification across compile, lint, and test phases in a CI/CD pipeline?

Automated code verification coordinates a 6-phase gate across compile, lint, test, secret scan, architecture, and code review. It enforces strict pass criteria in CI/CD and PR workflows, ensuring only changes passing all phases are allowed through.

Can I automatically fix code review issues before opening a pull request?

Yes, you can automatically fix code review issues using an auto-fix loop. The code review phase supports up to three review cycles with auto-fix iterations to resolve detected issues without manual intervention before merging.

What is the best way to prevent secret leakage and architectural regressions during code changes?

Preventing secret leakage and architectural regressions requires dedicated verification phases. The pipeline includes specific secret scanning and architecture checks to prevent credential leakage and architectural drift before code changes are approved.

Does the verification pipeline support multi-gate validation for PR workflows?

Yes, the verification pipeline supports multi-gate validation for PR workflows. It provides deterministic gating by enforcing strict pass criteria across all six phases, ensuring consistent quality and readiness across teams.

How many auto-fix cycles are allowed during the code review phase?

The code review phase allows up to three auto-fix cycles. These iterations automatically resolve issues found during review, reducing manual intervention and ensuring code meets strict pass criteria before merging.