jr-test

Audit test coverage across unit, integration, and end-to-end layers without changing production code.

3|1|Updated Mar 28, 2026

Search Tags:#automation #testing #verification #audit #ci-cd #quality-assurance #test-governance

Ready to run

npx skills add https://github.com/rusi/junior --skill jr-test

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jr-test
Source: https://github.com/rusi/junior/tree/main/agents/skills/jr-test
Command: npx skills add https://github.com/rusi/junior --skill jr-test

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Independent assessment of test quality and coverage, eliminating weak patterns and enforcing multi-layer quality gates to ensure credible software delivery.

Core Features & Use Cases

Acts as chief software test engineer to validate tests, prune anti-patterns, and enforce unit/integration/end-to-end coverage.
Maintains strict boundaries: no production code changes during /jr-test; only tests, fixtures, utilities, and minimal harness wiring.
Provides a structured handoff to /jr-implement when defects are found or coverage gaps remain.

Quick Start

Act as chief software test engineer for a story, audit the existing test landscape, and enforce strong end-to-end test coverage without changing production code.

Frequently Asked Questions about jr-test

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

FAQPage Schema

How do I audit existing test coverage for weak patterns across unit, integration, and end-to-end layers?▼

Test governance enforces multi-layer quality gates by auditing existing tests, eliminating weak patterns, and validating coverage across unit, integration, and end-to-end layers. It provides an independent assessment of test quality to ensure credible software delivery without altering production code.

Can I fix production code defects found during an automated test suite audit?▼

No, you cannot fix production code defects during the test audit. The Skill maintains strict boundaries by prohibiting production code changes, restricting modifications to tests, fixtures, utilities, and minimal harness wiring, then providing a structured handoff to implementation when defects are found.

What is the best way to enforce quality assurance without changing production code?▼

The best way to enforce quality assurance without changing production code is to audit the test landscape and harden test suites end-to-end. This approach validates tests, prunes anti-patterns, and enforces coverage while restricting changes to tests and fixtures only.

Does the test audit process integrate with CI-CD pipelines for continuous verification?▼

Yes, the test audit process supports CI-CD integration through test governance and automated verification. It audits the existing test landscape, enforces strong end-to-end test coverage, and tracks progress to maintain quality assurance standards across continuous delivery workflows.

How do I handle coverage gaps identified during end-to-end test hardening?▼

To handle coverage gaps identified during end-to-end test hardening, the Skill provides a structured handoff to implementation. It explicitly routes discovered defects and remaining coverage gaps to a downstream implementation phase while ensuring no production changes occur during the audit.