skills.rest
LanternOps
LanternOpsOFFICIAL
Explore all skills by this author →
GitHub

feature-testing

Automates UI, API, and agent feature verification using Playwright MCP and diagnostic logs.

73|23|Updated Jan 14, 2026
Search Tags:#qa#verification#end-to-end#playwright#ui-testing#api-testing#agent-deployment
One-click install
npx skills add https://github.com/LanternOps/breeze --skill feature-testing-lanternops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: feature-testing
Source: https://github.com/LanternOps/breeze/tree/main/.claude/skills/feature-testing
Command: npx skills add https://github.com/LanternOps/breeze --skill feature-testing-lanternops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

After implementing a feature, verify that it works correctly across user interfaces, APIs, and the agent workflow to prevent regressions and ensure quality.

Core Features & Use Cases

  • End-to-end verification across the UI, API, and agent layers using Playwright MCP, diagnostic logs, and controlled deployments.
  • Structured test logging and traceability for feature changes and release readiness.
  • Use Case: When a feature is complete, run this skill to validate UI flows, API responses, and agent behavior in a coherent, repeatable process.

Quick Start

Invoke this skill after implementing a feature to verify end-to-end functionality across UI, API, and agent layers using Playwright MCP, dev-push, and diagnostic logs.

Frequently Asked Questions about feature-testing

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

FAQPage Schema
How do I automate end-to-end feature verification across UI, API, and agent layers?▼

End-to-end feature verification is automated by validating UI flows with Playwright MCP, pushing device deployments via make dev-push, and checking agent behavior through diagnostic-logs API verification. This process ensures coherent, repeatable test coverage across all layers after implementing features.

What is the best way to validate agent behavior and API responses after a bug fix?▼

Validating agent behavior and API responses after a bug fix is best done using diagnostic-logs API verification combined with structured test logging. This approach traces feature changes and confirms release readiness by testing typical and edge case scenarios across the API and agent layers.

Can I use Playwright MCP for testing UI flows in typical and edge case scenarios?▼

Yes, Playwright MCP is used for testing UI flows in both typical and edge case scenarios. It drives end-to-end verification across the user interface layer, ensuring that feature changes and bug fixes work correctly without causing regressions in the UI.

Does end-to-end testing support controlled deployments via make dev-push?▼

Yes, end-to-end testing supports controlled deployments via the make dev-push command. This feature allows you to push updates to devices and validate the deployment alongside UI flows and agent behavior in a structured, repeatable verification process.

When do I need structured test logging for feature changes and release readiness?▼

Structured test logging for feature changes is needed after implementing a feature or bug fix to ensure release readiness. It provides traceability for end-to-end verification across UI, API, and agent layers, confirming that typical and edge case scenarios pass before deployment.

Related Skills

Explore More Software Engineering Skills→
AlejandroFiginiAlejandroFigini

ios-fix

Read iOS source, apply fixes, rebuild, redeploy, and verify on a real device.

Community
Advanced
mattleonard16mattleonard16

test-fixing

Group failing test errors into clusters and validate fixes before release.

Community
Advanced
liwooliwoo
16

playwright-ui-test

Automate UI integrity checks for Goravel Inertia apps with Playwright MCP.

Community
Advanced
krzemienskikrzemienski
2

fullstack-validation

Validate end-to-end data flow from database to API to frontend.

Community
Advanced