skills.rest
jbreel77888
jbreel77888COMMUNITY
Explore all skills by this author →
GitHub

testing

Define required unit, integration, e2e, and contract tests for code changes in monorepos.

Updated Aug 27, 2026
Search Tags:#testing#unit testing#monorepo#test coverage#code changes#CI gates#enterprise quality
One-click install
npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill testing-jbreel77888
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/jbreel77888/Agent-AiNorx/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/jbreel77888/Agent-AiNorx --skill testing-jbreel77888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

In a large monorepo with multiple applications and shared packages, code changes are frequently merged without accompanying tests, leading to flaky builds, undetected regressions, and failed enterprise audit requirements for code reliability and quality.

Core Features & Use Cases

  • Test Type Mapping: Clearly defines which test type (unit, integration, e2e, contract, etc.) is required for every kind of code change, from pure utility functions to HTTP routes and database schemas.
  • Local & CI Enforcement: Provides exact commands to run tests locally and documents CI gates that automatically block pull requests that lack required tests or fail coverage thresholds.
  • Standardized Conventions: Establishes non-negotiable rules for deterministic, isolated tests including factory usage, no shared state, and typecheck requirements to ensure consistent, reliable test results across the team.
  • Use Case: When you refactor a React component used in the customer checkout flow, this skill guides you to add a co-located unit test, run the relevant test suite locally, and confirm the CI coverage gate passes before submitting your pull request.

Quick Start

Use the testing skill to add a required unit test for the new utility function you just added to the shared payments package and verify it passes locally before committing your change.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I enforce unit testing for every code change in a monorepo?▼

To enforce unit testing for every code change in a monorepo, you need mandatory test inclusion rules and CI gates that block pull requests lacking required tests. This ensures all behavioural modifications have accompanying tests before reaching production.

What type of tests do I need for database schema and HTTP route changes?▼

Database schema changes and HTTP route modifications require specific test types like integration and contract tests. Mapping the correct test type to each code change category ensures deterministic, isolated test execution and meets enterprise quality standards.

How do I prevent untested code modifications from reaching production?▼

To prevent untested code modifications from reaching production, implement CI gate enforcement rules that automatically block pull requests failing coverage thresholds or lacking required tests for behaviour-modifying changes across shared packages.

Does CI gate test coverage work with React components in a shared packages monorepo?▼

CI gate test coverage works with React components in a shared packages monorepo by requiring co-located unit tests for refactored components. Running the relevant test suite locally and confirming coverage thresholds pass ensures reliable merges.

Why do my monorepo builds fail enterprise audit requirements for code reliability?▼

Monorepo builds fail enterprise audit requirements for code reliability when code changes merge without accompanying tests, leading to undetected regressions. Standardized conventions for deterministic, isolated tests with factory usage and no shared state resolve this.

Related Skills

Explore More Software Engineering Skills→
sgcarstrendssgcarstrends
21

coverage-analysis

Analyze Vitest coverage across monorepo packages and generate reports.

Official
Advanced
vecearvecear

quality-gates-enforcer

Enforce coverage, linting, type checking, and security thresholds in CI pipelines.

Community
Advanced
Sir-chawakornSir-chawakorn
9

debug-flaky-tests

Diagnose non-deterministic test failures by classifying root causes like shared state and race conditions.

Community
Advanced
chongdashuchongdashu
85

playwright-testing

Plan, implement, and debug Playwright MCP tests across unit, integration, E2E, and visual layers.

Community
Intermediate