autonomous-qa-and-testing

Runs test suites, linters, and quality gates across TypeScript, Go, and Python projects.

Updated May 16, 2026
One-click install
npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill autonomous-qa-and-testing-alimtvnetwork
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: autonomous-qa-and-testing
Source: https://github.com/alimtvnetwork/img-pdf-v2/tree/main/.agents/skills/autonomous-qa-and-testing
Command: npx skills add https://github.com/alimtvnetwork/img-pdf-v2 --skill autonomous-qa-and-testing-alimtvnetwork

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating tests, linters, and CI checks across polyglot codebases is error-prone, and running full suites at the wrong time wastes resources. This Skill enforces disciplined, gated execution of testing and quality verification so regressions are caught without disrupting routine development. ## Core Features & Use Cases - Polyglot Test Execution: Runs npm run test and npm run lint for TypeScript/React, go test ./... for Go, and targeted linters for routine changes. - Gated CI Runner: Restricts the full local CI runner (06-cicd-local-runner.py) to explicit owner commands or pre-release ceremonies, with --run-tests for release gates. - Incremental Test Inventory: Maintains .ai-memory/test-inventory.json with per-test timings, running only tests affected by changed files, with dual-queue worker pools separating slow and fast tests. - Use Case: During a release ceremony, invoke the full quality gate to run the complete test suite, verify git hygiene, and record modified files atomically before pushing to GitHub. ## Quick Start Ask the agent to run the pre-release quality gate and verify all tests pass before pushing the release branch.

Frequently Asked Questions about autonomous-qa-and-testing

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

FAQPage Schema
How do I run tests in a polyglot repository with TypeScript and Go?

Run `npm run test` and `npm run lint` for TypeScript/React code and `go test ./...` for Go packages. For routine changes, run targeted linters only on modified files instead of the full suite.

How to run a full CI pipeline locally before a release?

Execute `python 03-ai-scripts/06-cicd-local-runner.py --run-tests` during the release ceremony. The full runner is restricted to explicit owner commands or pre-release gates, not routine development turns.

Can I run the full test suite during routine development?

No. Full test suites and the CI runner are prohibited in standard turns; only targeted single-file linters are allowed. Full runs require an explicit owner command or the pre-release quality gate.

How does incremental test caching speed up test runs?

A test inventory in `.ai-memory/test-inventory.json` maps tests to target files with baseline timings. Subsequent runs execute only tests whose target or test files changed, skipping unaffected tests.

Where are test failure logs stored?

Failed tests and gates write logs to `.ai-memory/temp/failures/<test-or-job>.log`. Passing tests produce no output artifacts, and all temporary files are isolated under `.ai-memory/temp/`.