validate-feature

Deploy a feature locally, run security scans, and generate OpenSpec compliance reports.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill validate-feature-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-feature
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/validate-feature
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill validate-feature-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, httpx, playwright, and includes scripts (resource) components.

What problem does it solve?

It addresses the need to ensure that newly implemented features are correctly deployed, pass health checks, meet security standards, and comply with OpenSpec specifications before merging.

Core Features & Use Cases

  • Deploy Locally: Spins up Docker services with DEBUG logging for realistic testing.
  • Smoke Tests: Verifies health endpoints, authentication, and CORS.
  • Security Scans: Runs OWASP Dependency‑Check and ZAP against the live service.
  • E2E Tests: Executes Playwright scenarios to validate end‑to‑end behavior.
  • Spec Compliance: Generates and updates OpenSpec compliance reports.
  • Flexible Phases: Allows skipping or selecting specific phases via flags.

Quick Start

Run the validate-feature skill with the change ID to generate a full validation report.

Frequently Asked Questions about validate-feature

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

FAQPage Schema
How do I validate a feature branch locally before merging?

To validate a feature branch locally, you can orchestrate Docker compose deployment, run pytest smoke tests, execute Playwright E2E tests, and generate OpenSpec compliance reports to verify the feature is ready for merge.

What does local feature validation with security scans and E2E tests involve?

Local feature validation involves deploying Docker services, verifying health endpoints with pytest, scanning dependencies with OWASP, running Playwright E2E tests, and checking OpenSpec compliance to ensure the feature meets security and functional standards.

Can I run only security scans and skip E2E tests during local validation?

Yes, local feature validation supports flexible phases, allowing you to skip or select specific phases like OWASP Dependency-Check or Playwright E2E tests via flags to focus on targeted verification.

Do I need Docker and Playwright to run OpenSpec compliance checks?

Docker compose is required for local deployment, while Playwright is needed for E2E tests; however, flexible phase flags let you run OpenSpec compliance checks independently without executing the full Docker and Playwright pipeline.

What is the best way to automate feature verification in an AI-assisted development pipeline?

The best way to automate feature verification is orchestrating Docker deployment, pytest smoke tests, OWASP security scans, Playwright E2E tests, and OpenSpec report generation to ensure new features pass health checks and security standards before merging.