LogoSkills

checklist

Systematic verification checklists for feature development completion and PR review. Reviews 11 items including structure verification, testing, security, performance, and internationalization.

Checklist#

A master checklist skill for feature development completion verification and PR review.

Scope and Capabilities#

Checklist Types#

TypePurposeKey Verification Items
Feature Complete Self-verification before development completion Structure, code generation, testing, documentation, i18n, performance, security, accessibility
PR Review Verification during code review Meta information, change scope, code quality, state management, testing, security

Quick Start#

Feature Completion Verification#

@checklist/feature-complete [feature_name]

PR Review#

@checklist/pr-review [PR number or link]

Feature Complete Verification Items (11)#

#ItemDescription
1Structure VerificationDomain/Data/Presentation layer completeness
2Code GenerationFreezed, Injectable, Route code generation
3TestingUnit/BLoC/Widget tests
4Documentationdartdoc, comments, TODO resolution
5InternationalizationTranslation keys, pluralization, parameters
6Performance Optimizationconst, buildWhen, ListView.builder
7Security ReviewHardcoding, input validation
8AccessibilitySemantics, touch target, color contrast
9Static AnalysisLint, formatting
10Integration VerificationiOS/Android build
11PR PreparationCommit messages, issue linking

PR Review Verification Items (10)#

#ItemDescription
1PR Meta InformationTitle convention, issue linking, labels
2Change ScopePurpose clarity, single purpose
3Code QualityArchitecture, naming, structure
4State ManagementBLoC, Freezed, error handling
5TestingNew tests, edge cases
6SecuritySecrets, logging, input validation
7PerformanceN+1, re-renders, caching
8InternationalizationHardcoded strings, translation keys
9AccessibilitySemantic labels, touch targets
10DocumentationAPI docs, Breaking Changes

Priority Classification#

Must-Have (cannot Approve)#

  • Build failure
  • Test failure
  • Security vulnerability
  • Undocumented Breaking Change
  • Architecture violation

Should-Have (can Approve after requesting improvements)#

  • Insufficient performance optimization
  • Insufficient test coverage
  • Insufficient documentation
  • Insufficient accessibility

Nice-to-Have (comment only)#

  • Naming improvement suggestions
  • Code style suggestions
  • Additional optimization suggestions

Additional Resources#