long-task-quality

Name: long-task-quality
Availability: InStock
Author: suriyel

Run predefined scripts to verify tests, coverage thresholds, and mutation scores.

178|43|Updated Feb 12, 2026

Search Tags:#testing #quality assurance #code coverage #verification #mutation testing #continuous integration

Ready to run

npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-quality

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: long-task-quality
Source: https://github.com/suriyel/longtaskforagent/tree/main/skills/long-task-quality
Command: npx skills add https://github.com/suriyel/longtaskforagent --skill long-task-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that code meets stringent quality standards by enforcing verification gates for tests, coverage, and mutation before a feature can be marked as complete.

Core Features & Use Cases

Automated Quality Gates: Implements sequential checks for test verification, code coverage, and mutation testing.
Evidence-Based Completion: Requires concrete proof of quality metrics before a feature is considered passing.
Use Case: After completing a TDD cycle for a new feature, use this Skill to automatically run all tests, check if coverage meets the 90% line and 80% branch threshold, and ensure the mutation score is above 80%, preventing incomplete or poorly tested code from being merged.

Quick Start

Use the long-task-quality skill to run all quality gates for the current feature.

Frequently Asked Questions about long-task-quality

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

FAQPage Schema

How do I enforce code coverage and mutation testing thresholds before merging a feature?▼

You can enforce code coverage and mutation testing thresholds by running this Skill to execute predefined scripts that validate test outputs against project-specific requirements, ensuring concrete quality evidence before marking a feature complete.

What are automated quality gates in continuous integration?▼

Automated quality gates are sequential validation checks for test verification, code coverage, and mutation testing scores that prevent software features from being marked as complete without fresh, verifiable evidence of quality.

Can I use this quality gate process after completing a TDD cycle?▼

Yes, you can use this quality gate process after a TDD cycle to automatically run all tests, validate if coverage meets the 90% line and 80% branch threshold, and ensure the mutation score is above 80%.

Does the mutation testing verification work without external dependencies?▼

Yes, the mutation testing verification works without external dependencies by executing predefined scripts and references to validate outputs against project-specific requirements for evidence-based completion.

What is the best way to prevent incomplete or poorly tested code from being merged?▼

The best way to prevent poorly tested code from being merged is to implement a multi-stage quality gate process that requires passing real test verification, coverage thresholds, and mutation testing scores before completion.