test-catalog-updater

Update TEST_CATALOG.md with test metrics, status, and failure details.

1|1|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill test-catalog-updater
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-catalog-updater
Source: https://github.com/DarkMonkDev/WitchCityRope/tree/main/.claude/skills/test-catalog-updater
Command: npx skills add https://github.com/DarkMonkDev/WitchCityRope --skill test-catalog-updater

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, awk, grep, sed, cp, and includes scripts (resource) components.

What problem does it solve?

Manual updates to test catalogs are error-prone and often neglected, leading to outdated information on test health, coverage, and status, making it impossible to track quality trends.

Core Features & Use Cases

  • Automated Metrics: Records test metrics (pass/fail counts, execution time, coverage) and updates the TEST_CATALOG.md after every test run.
  • Status Tracking: Automatically updates test status (PASSING, FAILING, FLAKY, NEW, ARCHIVED) and appends failure details for quick investigation.
  • Single Source of Truth: Maintains TEST_CATALOG.md as the definitive record of all test files and their health, crucial for Phase 4 validation.
  • Use Case: After running your E2E test suite, use this Skill to automatically update the TEST_CATALOG.md with the latest results, ensuring the orchestrator has real-time data on test health.

Quick Start

Update the test catalog with unit test results: 45 passed, 0 failed, 12.3s execution, 85% coverage.

Frequently Asked Questions about test-catalog-updater

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

FAQPage Schema
How do I automatically update my test catalog after running tests?

Automatically update your TEST_CATALOG.md after test execution by applying this Skill to record pass/fail counts, execution time, coverage percentages, and timestamps. It runs in local environments or CI/CD pipelines, maintaining a single source of truth for test health and status.

What test metrics does automated catalog updating capture?

Automated catalog updating captures passed and failed test counts, execution duration, code coverage percentage, test status (PASSING, FAILING, FLAKY, NEW, ARCHIVED), failure details, and last-updated timestamps, enabling trend tracking and quality assessment.

Can I use test catalog automation in CI/CD pipelines?

Yes, this Skill integrates into CI/CD pipelines to automatically update TEST_CATALOG.md after unit, integration, or E2E test runs, eliminating manual catalog maintenance and ensuring the orchestrator has real-time test health data.

How does automated test status tracking work?

The Skill calculates pass rates from test results, determines overall status (PASSING, PARTIAL, or FAILING), logs detailed failure information for investigation, and updates section-specific catalog entries with current state and timestamps.

What backup and validation does test catalog automation provide?

The Skill creates backups before modifications, validates parameters, recalculates pass-rate thresholds, and logs comprehensive failure details, protecting catalog integrity while ensuring accurate status determination and transformation history.

Do I need manual intervention after running tests if using catalog automation?

No, the Skill eliminates manual updates by automatically recording metrics and status to TEST_CATALOG.md post-execution, reducing error and keeping documentation current without human intervention.