testing-implementation

Create and run unit and integration tests after feature implementation.

1|Updated Apr 12, 2026

Search Tags:#workflow #testing #code-quality #mocking #quality-assurance #unit-tests #test-coverage

Ready to run

npx skills add https://github.com/fascari/ai-config --skill testing-implementation-fascari

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-implementation
Source: https://github.com/fascari/ai-config/tree/main/skills/testing-implementation
Command: npx skills add https://github.com/fascari/ai-config --skill testing-implementation-fascari

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that testing happens consistently after feature work, preventing gaps in test coverage and aligning implementation with quality goals.

Core Features & Use Cases

Writes unit tests that cover new or modified features according to project conventions.
Validates test coverage against defined thresholds and reports gaps.
Guides the creation of integration tests where applicable and coordinates test data helpers.
Facilitates step-by-step execution of tests after feature completion and supports iterative refinement based on feedback.

Quick Start

Invoke this skill after completing feature implementation to generate and run tests following project standards.

Frequently Asked Questions about testing-implementation

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

FAQPage Schema

How do I generate unit tests after completing a feature implementation?▼

To generate unit tests after feature implementation, you need a skill that reads project conventions from .github/instructions and .github/plans, then writes and runs tests validating new code against defined coverage thresholds.

What is the best way to validate test coverage against project thresholds?▼

Validating test coverage requires executing tests after feature work and reporting gaps. The process reads guidelines from .github/instructions and .github/plans to ensure test artifacts meet your standard project quality assurance conventions.

Can I create integration tests and coordinate test data helpers using this approach?▼

Yes, creating integration tests and coordinating test data helpers is supported. The approach guides step-by-step execution of tests after feature completion, facilitating iterative refinement based on feedback within your project's conventions.

Do I need specific guidelines in .github/instructions to shape test artifacts?▼

Yes, you need guidelines in .github/instructions and .github/plans to shape test artifacts and reporting. The testing workflow relies on these files to align implementation with quality goals and ensure consistent test coverage.

Why does test coverage gap prevention matter after feature work?▼

Preventing test coverage gaps matters because it ensures testing happens consistently after feature work, aligning implementation with quality goals and validating that new or modified features meet project conventions.

Does testing-implementation support iterative test refinement based on feedback?▼

Yes, testing-implementation supports iterative test refinement based on feedback. It facilitates step-by-step execution of tests after feature completion, allowing you to refine unit and integration tests until coverage goals are met.