qa-learn

Count and prune stale QA knowledge base entries under .claude/qa-knowledge.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill qa-learn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-learn
Source: https://github.com/ArthTech-AI/Marketplace-extensions/tree/main/skills/qa-learn
Command: npx skills add https://github.com/ArthTech-AI/Marketplace-extensions --skill qa-learn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you inspect and maintain a self-improving QA knowledge base so you can quickly understand what has been learned, what remains uncovered, and what should be cleaned up.

Core Features & Use Cases

  • Incident review: Counts covered and uncovered incidents in the QA knowledge base and surfaces their titles.
  • Learning metrics: Summarizes promoted tests, bug patterns, coverage gaps, and challenger log performance in one structured view.
  • Stale-entry cleanup: Prunes outdated covered incidents, orphaned promoted tests, resolved coverage gaps, and old challenger log entries.
  • Use case: A QA lead can run a quick health check before a release to see whether recent issues are captured and whether the knowledge base needs cleanup.

Quick Start

Use the qa-learn skill to show QA knowledge base stats for incidents, promoted tests, bug patterns, coverage gaps, and challenger activity.

Frequently Asked Questions about qa-learn

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

FAQPage Schema
How do I clean up stale QA knowledge base entries for resolved incidents?

To clean up stale QA knowledge base entries, prune outdated covered incidents, orphaned promoted tests, resolved coverage gaps, and old challenger log entries based on their age, provenance, and coverage status.

What is QA knowledge base pruning and when do I need it?

QA knowledge base pruning is the process of reviewing and removing outdated records under .claude/qa-knowledge. You need it before a release to ensure recent issues are captured and outdated entries are removed.

Can I track incident coverage status within the Claude Code QA workflow?

Yes, you can track incident coverage status within the Claude Code QA workflow by counting covered and uncovered incidents in the knowledge base and surfacing their titles for review.

How do I review promoted tests and bug patterns before a software release?

Review promoted tests and bug patterns before a release by running a quick health check that summarizes learning metrics, coverage gaps, and challenger log performance in one structured view.

What types of outdated QA records should be pruned from a knowledge base?

Outdated QA records that should be pruned include stale covered incidents, orphaned promoted tests, resolved coverage gaps, and old challenger log entries determined by age and provenance.