How does this skill help with test coverage?

It automatically checks if new functionality meets the required threshold, specifically targeting 90% coverage or higher.

When is the best time to trigger this skill?

You should use it after you have finished implementing a feature or fix, but before you create a pull request or mark the issue as resolved.

What is the primary purpose of the Definition of Done skill?

It validates that all requirements and quality standards of a specific task are met before the work is considered finished.

Does this skill update my documentation automatically?

It doesn't write the documentation for you, but it verifies if the documentation and CHANGELOG.md files have been appropriately updated to reflect your changes.

Definition of Done Validator

Name: Definition of Done Validator
Author: jarosser06

byjarosser06

•

Productivity & Workflow

Validates completed work against issue requirements and quality standards to ensure all acceptance criteria are met before submission.

About

The Definition of Done skill provides a systematic framework for Claude to verify that a task is truly complete. It automates the final review process by mapping implemented changes back to original issue requirements, checking for high test coverage (≥90%), ensuring linting compliance, and verifying that documentation and changelogs have been updated. This skill is essential for maintaining high engineering standards and reducing the back-and-forth during the pull request review stage.

Key Features

Automated test coverage verification (≥90%)
Documentation and CHANGELOG update checks
3 GitHub stars
Requirement traceability mapping
Standardized validation reporting
Linting and quality gate enforcement

Use Cases

Ensuring consistent project documentation and changelog standards
Verifying feature completeness before opening a pull request
Performing final quality assurance on bug fixes

About

Key Features

Automated test coverage verification (≥90%)
Documentation and CHANGELOG update checks
3 GitHub stars
Requirement traceability mapping
Standardized validation reporting
Linting and quality gate enforcement

Use Cases

Ensuring consistent project documentation and changelog standards
Verifying feature completeness before opening a pull request
Performing final quality assurance on bug fixes