skills.rest
anotherben
anotherbenCOMMUNITY
Explore all skills by this author →
GitHub

run-verification

Run lint, unit tests, and conditional E2E tests for code changes.

6|Updated Mar 18, 2026
Search Tags:#testing#e2e#verification#pipeline#lint#unit-tests
One-click install
npx skills add https://github.com/anotherben/claude-harness --skill run-verification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: run-verification
Source: https://github.com/anotherben/claude-harness/tree/main/skills/run-verification
Command: npx skills add https://github.com/anotherben/claude-harness --skill run-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the validation of code changes by running lint, unit tests, and conditional end-to-end tests to ensure code health across the project.

Core Features & Use Cases

  • Lint Check: runs static analysis to catch style issues and potential errors early.
  • Unit & End-to-End Tests: orchestrates unit tests and, when UI changes are detected, runs E2E tests for regression coverage.
  • Clear Feedback: aggregates results and produces a concise report for quick remediation.

Quick Start

Run the verification pipeline after every code change to confirm the codebase remains healthy.

Frequently Asked Questions about run-verification

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

FAQPage Schema
How do I run lint and unit tests automatically after code changes?▼

Run a verification pipeline after every code change to execute lint checks, unit tests, and conditional E2E tests. This orchestrates static analysis and test suites to validate code health and provides a concise report for quick remediation.

How does conditional E2E testing work for UI changes?▼

Conditional E2E testing triggers end-to-end tests specifically when UI changes are detected. This ensures regression coverage for interface modifications without unnecessarily running E2E suites for backend-only updates.

What's the best way to automate a verification pipeline for rapid feedback?▼

The best way to automate a verification pipeline for rapid feedback is to orchestrate lint, unit tests, and conditional E2E tests. This pipeline aggregates results and produces a concise report, ensuring code health and enabling quick remediation.

Does this verification pipeline work for projects without UI changes?▼

Yes, the verification pipeline works for projects without UI changes by running lint and unit tests. End-to-end tests are conditional and only triggered when UI modifications are detected, making the pipeline suitable for backend-only codebases.

Why do I need to run E2E tests only when UI changes are detected?▼

Running E2E tests only when UI changes are detected saves time by avoiding unnecessary end-to-end execution for backend-only updates. This conditional trigger ensures regression coverage for interface modifications while maintaining rapid feedback.

Related Skills

Explore More Software Engineering Skills→
ianyimiianyimi
1

Global Validation

Enforce global validation standards across code generation, review, linting, and CI checks.

Community
Basic
raineraine
2.1k

merge

Commit staged changes, rebase onto the configured base branch, and merge with cleanup.

Community
Basic
barrydobsonbarrydobson

devops

Advocate DevOps principles including CI/CD, IaC, automated testing, monitoring, and security scanning for delivery pipelines.

Community
Intermediate
soniqosoniqo
1.1k

test

Run Swift unit or end-to-end test suites against a local codebase.

Official
Basic