<< All versions
Skill v1.0.1
currentAutomated scan100/100majiayu000/claude-skill-registry/definition-of-done
3 files
──Details
PublishedJune 7, 2026 at 03:41 PM
Content Hashsha256:cf4a95ef8e04aeb1...
Git SHA8ecbb297e90a
Bump Typepatch
──Files
Files (1 file, 2.5 KB)
SKILL.md2.5 KBactive
SKILL.md · 87 lines · 2.5 KB
version: "1.0.1"
Definition of Done
Description: Validate completed work against issue requirements and acceptance criteria. Use when finishing work on an issue to ensure all requirements are met.
When to Use This Skill
- After implementing a feature or fix
- Before creating a pull request
- When validating work against issue acceptance criteria
- To ensure nothing was missed from the original requirements
Quick Reference
Validation Checklist
- All issue requirements implemented
- Acceptance criteria met
- Tests cover new functionality (≥90% coverage)
- Linting passes with zero errors
- Documentation updated if needed
- CHANGELOG.md updated
- No hardcoded values or credentials
Resource Guides
📖 Issue Validation Guide
Comprehensive guide for validating work against issue requirements and acceptance criteria.
Use when: Checking if all issue requirements have been met.
📖 Common Gaps
Common things developers forget when completing issues.
Use when: Performing final validation before marking work complete.
Key Principles
- Requirement Traceability: Every requirement in the issue should be addressed
- Acceptance Criteria: All acceptance criteria must be met
- Test Coverage: New code must be tested (≥90% coverage)
- Quality Gates: All automated checks must pass
- Documentation: User-facing changes documented appropriately
Validation Process
- Fetch Issue Details: Get full issue description and requirements
- Map Requirements: Identify each requirement and acceptance criterion
- Verify Implementation: Check that each requirement has been implemented
- Check Test Coverage: Ensure tests exist for new functionality
- Validate Quality: Confirm linting and tests pass
- Review Documentation: Ensure docs/CHANGELOG updated if needed
- Report Status: Provide clear summary of what's complete and any gaps
Output Format
Provide validation results in this format:
markdown
## Definition of Done Validation### Issue: #{number} - {title}#### Requirements Status-✅ Requirement 1: Description-✅ Requirement 2: Description-❌ Requirement 3: Description (Not implemented)#### Acceptance Criteria-✅ Criterion 1-✅ Criterion 2#### Quality Gates-✅ Tests pass (90%+ coverage)-✅ Linting passes-✅ CHANGELOG.md updated-⚠️ Documentation needs update#### Summary{brief summary of validation results}#### Action Items (if any)-Item 1-Item 2