final-check-automation

Automate final deployment checks with Playwright tests, version analysis, and security audits.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/garimto81/claude --skill final-check-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: final-check-automation
Source: https://github.com/garimto81/claude/tree/main/.claude/skills/final-check-automation
Command: npx skills add https://github.com/garimto81/claude --skill final-check-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the critical final checks before deployment, including end-to-end testing, version determination, and security scans, reducing manual effort and potential errors.

Core Features & Use Cases

  • Automated E2E Testing: Runs Playwright tests and attempts automatic fixes for failures.
  • Version Determination: Analyzes commit history to decide on MAJOR, MINOR, or PATCH version bumps.
  • Security & Performance Scans: Executes security audits (pip-audit, npm audit) and performance checks.
  • Use Case: Before merging a feature branch, automatically run all E2E tests, determine the correct semantic version for the release, and perform a security scan to ensure the code is production-ready.

Quick Start

Execute the final check automation script to begin the E2E testing and security scan process.

Frequently Asked Questions about final-check-automation

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

FAQPage Schema
How do I automate end-to-end testing and security scans before a deployment?

Automated end-to-end testing and security scans are orchestrated by executing the final check automation script, which runs Playwright tests, pip-audit, and npm audit to verify production readiness. It coordinates these tools to reduce manual verification effort before merging feature branches.

What is the best way to determine semantic versioning from conventional commit history?

Semantic versioning is determined by analyzing conventional commit history to decide between MAJOR, MINOR, or PATCH version bumps. The automated workflow inspects git commit messages to calculate the correct release version automatically, eliminating manual version tracking errors.

Can I run Playwright E2E tests and automatically fix failures during the final verification workflow?

Playwright E2E tests are executed as part of the final verification workflow, and the automation attempts automatic fixes for test failures. This ensures end-to-end tests pass before deployment by orchestrating test execution and applying corrections when possible.

Does this automation tool support both pip-audit and npm audit for security vulnerability scanning?

Both pip-audit and npm audit are supported for security vulnerability scanning within the final check workflow. The automation executes these security tools alongside performance checks to ensure the codebase is free from known vulnerabilities before production deployment.

How do I run a final verification check for production readiness on a feature branch?

Final verification checks for feature branches are run by executing the final check automation script, which orchestrates E2E testing, version determination, and security scanning. This automated workflow ensures all critical pre-deployment validations pass before merging.

When should I not use automated final checks for deployment verification?

Automated final checks may not suit workflows lacking conventional commit history for version determination or projects without Playwright, pip-audit, or npm audit configured. The automation depends on git history analysis and these specific testing and security tools to function correctly.