implementation-review
Self-feedback review loop to verify implementation matches specification. Use with --mode quick/standard/thorough to control review depth. Default is thorough (3 consecutive passes). (user)
Browse published AI skills maintained by teliha. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
12Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Self-feedback review loop to verify implementation matches specification. Use with --mode quick/standard/thorough to control review depth. Default is thorough (3 consecutive passes). (user)
Analyze test coverage and add new test cases to improve coverage without changing implementation
Translate specification files to Japanese while preserving technical accuracy and formatting
Expert guidance for creating and maintaining GitHub Actions workflows and reusable workflows with security best practices
Review specifications for completeness, clarity, testability, and quality. Use with --mode quick/standard/thorough to control review depth. Default is thorough (3 consecutive passes). (user)
Analyze specification files for contradictions, inconsistencies, and ambiguities
Analyze and fix CI/CD pipeline failures including build errors, test failures, and linting issues
Fix lint and static analysis warnings one at a time with proper prioritization
Generate Japanese documentation from spec files. Use AUTOMATICALLY after writing or editing any file matching specs/**/*.md (excluding specs/**/docs/*). Also use when user says "generate spec docs", "spec docs"...
Deep security analysis for Solidity smart contracts with DeFi context
Comprehensive code review for pull requests with quality, security, and best practices analysis
Generate a specification file from user input/requirements. Use when user says "generate spec", "create spec", "write spec", "spec from requirements", or provides feature requirements and asks to create a spec....
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.