skills.rest
akkpol
akkpolCOMMUNITY
Explore all skills by this author →
GitHub

qa-agent

Run TypeScript, Vitest, and Playwright tests and log failures to .codex/issues.

Updated Aug 23, 2026
Search Tags:#typescript#vitest#testing#qa#playwright#ci-cd#issue-logging
One-click install
npx skills add https://github.com/akkpol/crafe-flow-nextjs --skill qa-agent-akkpol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-agent
Source: https://github.com/akkpol/crafe-flow-nextjs/tree/main/.codex/skills/qa-agent
Command: npx skills add https://github.com/akkpol/crafe-flow-nextjs --skill qa-agent-akkpol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines quality assurance for software projects by running TypeScript checks, Vitest unit tests, and Playwright E2E tests, and by logging all failures to a centralized issue registry without modifying code.

Core Features & Use Cases

  • TypeScript checks to surface compile-time errors early
  • Vitest unit tests to validate code logic
  • Playwright E2E tests to verify user flows
  • Centralized issue logging in .codex/issues for PM analysis
  • Strict rule: never modify source code; only report findings

Quick Start

Start by running the QA agent in your project to execute type checks, unit tests, and Playwright E2E tests, then review the generated YAML issue logs in .codex/issues.

Frequently Asked Questions about qa-agent

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

FAQPage Schema
How do I run TypeScript, Vitest, and Playwright tests without modifying source code?▼

To run tests without modifying source code, execute the QA agent to perform TypeScript checks, Vitest unit tests, and Playwright E2E tests, logging failures to a centralized registry while enforcing strict separation between testing and code modification.

What is the best way to log QA issues for project manager review in a CI/CD pipeline?▼

The best way to log QA issues for PM review is to execute TypeScript, Vitest, and Playwright E2E tests, capturing all failures as standardized YAML logs in the .codex/issues registry for assignment and analysis without applying fixes.

Can I use this QA agent to capture TypeScript compile-time errors and E2E test results together?▼

Yes, you can capture TypeScript compile-time errors and Playwright E2E test results together by running the agent, which surfaces issues across type checks, unit tests, and user flows into a unified .codex/issues registry.

Does the automated testing workflow attempt to fix unit-test failures it detects?▼

No, the automated testing workflow does not attempt to fix detected unit-test failures; it strictly applies safe testing practices to identify Vitest failures and logs them for PM review without modifying any source code.

How do I review logged issues after running TypeScript checks and E2E tests?▼

To review logged issues after running TypeScript checks and E2E tests, navigate to the .codex/issues directory to inspect the generated YAML issue logs, which capture failures for project manager analysis and assignment.

Why does my QA testing workflow need a centralized issue registry?▼

Your QA testing workflow needs a centralized issue registry to consistently capture TypeScript errors, unit-test failures, and Playwright E2E results across codebases, ensuring standardized logging formats for safe PM review without code modifications.

Related Skills

Explore More Software Engineering Skills→
limkyuleelimkyulee

vue-layer-test

Generate Vue 3 Vitest and E2E test configurations from CONFIG settings.

Community
Advanced
semicolon-devteamsemicolon-devteam

iteration-tracker

Track test iterations and outcomes for GitHub issues via issue comments.

Official
Advanced
koderoverkoderover
7

sonar

Retrieve and analyze SonarQube code quality metrics and quality gate statuses.

Official
Intermediate
guille-galloguille-gallo

setup-pre-commit

Automate pre-commit hook setup with Husky and lint-staged for Git repositories.

Community
Intermediate