qa-rampage

Name: qa-rampage
Availability: InStock
Author: sobhan

Run automated typechecking, linting, testing, and browser-based user journeys.

1|Updated May 12, 2026

Search Tags:#quality assurance #qa #automated testing #browser testing #application testing

Ready to run

npx skills add https://github.com/sobhanashine/nazarato --skill qa-rampage

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-rampage
Source: https://github.com/sobhanashine/nazarato/tree/main/.agents/skills/qa-rampage
Command: npx skills add https://github.com/sobhanashine/nazarato --skill qa-rampage

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, eslint, playwright, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that your application undergoes a comprehensive quality assurance check before release, reducing the risk of bugs and improving user experience.

Core Features & Use Cases

Automated Checks: Runs typecheck, lint, tests, and production build to catch issues early.
Browser Walk-through: Manually tests each route's page states, responsiveness, and accessibility.
Combined Report: Provides a single pass/fail report for easy review.

Quick Start

To initiate a QA Rampage, use the command: 'qa-rampage'

Frequently Asked Questions about qa-rampage

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

FAQPage Schema

How do I run an automated QA pass before shipping my application?▼

To run an automated QA pass, execute a command that triggers typechecking, linting, testing, and a production build. This process catches application issues early and generates a single combined pass/fail report for review.

What is a browser walk-through in application testing?▼

A browser walk-through in application testing is a manual check of each route's page states, responsiveness, and accessibility. It requires manual intervention to navigate the application and verify user journeys using Playwright.

Do I need Node.js and Playwright to run automated testing and linting?▼

Yes, you need Node.js and Playwright to run this automated testing and linting process. Node.js executes the typecheck, lint, and test commands, while Playwright is required for the browser-based user journey checks.

Can I use TypeScript and ESLint for a pre-release quality assurance check?▼

Yes, you can use TypeScript and ESLint for a pre-release quality assurance check. The process runs TypeScript typechecking and ESLint linting alongside tests and builds to catch issues before release and improve user experience.

What's the best way to combine typechecking, linting, and browser testing into one report?▼

The best way to combine typechecking, linting, and browser testing into one report is to run a comprehensive QA rampage. It executes automated checks and a manual browser walk-through, producing a single pass/fail report for quick review.

Why does browser testing require manual intervention during the QA process?▼

Browser testing requires manual intervention during the QA process to accurately evaluate each route's page states, responsiveness, and accessibility. An automated script cannot fully substitute for human verification of visual user journeys.