test-coverage-improvement-expert
Analyze test coverage and add new test cases to improve coverage without changing implementation
Découvrez les skills Données et IA, comparez leurs dépôts et consultez leurs instructions.
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....
Object-oriented design principles including object calisthenics, dependency inversion, fail-fast error handling, feature envy detection, and intention-revealing naming. Activates during code refactoring, design...
Research-driven investigation skill for validating solutions and exploring documentation. Never ask questions you can answer yourself through research. Use WebFetch, WebSearch, and testing to validate ideas bef...
Enforces brevity and signal-over-noise in all outputs. Eliminates verbose explanations, filler phrases, and unnecessary elaboration. Use when documentation, artifacts, or responses need to be maximally concise...
Ensures questions are answered literally before taking action. Triggers on user input containing '?' or patterns like 'why did you...?', 'will that work?', 'have you considered...?'. Use when user asks about yo...
Quick persona switching. Triggers: 'switch persona', 'switch to X', 'become X'. Lists personas, reads selected file, switches immediately.
This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific...
Strict test-driven development state machine with red-green-refactor cycles. Enforces test-first development, meaningful failures, minimum implementations, and full verification. Activates when user requests: '...
Systematic debugging methodology that eliminates guessing and speculation. Add instrumentation to gather specific data that fully explains the problem. Evidence before hypothesis. Observation before solution.
Comprehensive data visualization skill covering visual execution and technical implementation. Includes perceptual foundations, chart selection, layout algorithms, and library guidance. Load on-demand when buil...
FOLLOW THE STATE MACHINE IN SKILL.MD. When user says 'continue': (1) FIRST: Run pwd, (2) Announce STATE: CHECK_STATUS, (3) Read .claude/session.md to check Status field, (4) Route based on Status. NEVER auto-ad...
Principles for writing effective, maintainable tests. Covers naming conventions, assertion best practices, and comprehensive edge case checklists. Based on BugMagnet by Gojko Adzic.
Professional, skeptical communication style focused on critical thinking and coaching. Never over-enthusiastic, always verifies before agreeing, challenges ideas constructively. Use when you want a persona to a...
Creates well-formed tasks following a template that engineers can implement. Use when creating tasks, defining work items, creating tasks from PRD, breaking down features, or converting requirements into action...
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.