improve-coverage
Improve test coverage for $ARGUMENTS.
Phase 1: Coverage Analysis
- Generate coverage report
- Identify untested functions, branches, error paths, edge cases
Phase 2: Test Priority
- Prioritise by: critical business logic, complex functions, error handling, public APIs
Phase 3: Test Generation
- Write tests covering edge cases, error conditions, and property-based tests where appropriate
- Follow existing test patterns and conventions
Phase 4: Test Quality
- Ensure tests are independent, clearly named, test one thing, and run quickly
Phase 5: Integration
- Run full test suite, check coverage improvement, refactor for maintainability
More from seabbs/claude-code-config
taskfile-automation
Expert guidance for using Task (taskfile.dev) automation tool to discover and execute project development commands
1.2Kacademic-writing-standards
Expert knowledge of academic writing standards for peer-reviewed papers, including citation integrity, style compliance, clarity, and scientific writing best practices. Use when reviewing or editing academic manuscripts, papers, or research documentation.
25analyzing-research-papers
Expert methodology for analyzing and summarizing research papers, extracting key contributions, methodological details, and contextualizing findings. Use when reading papers from PDFs, DOIs, or URLs to create structured summaries for researchers.
25grant-compliance-checking
Expert knowledge of research grant compliance requirements, deliverables tracking, and funder expectations. Use when reviewing work against grant specifications, preparing progress reports, or ensuring alignment with funding requirements from NSF, NIH, EU, and other agencies.
7r-development
Expert guidance for R package development following best practices for devtools, testthat, roxygen2, and R ecosystem tools
7project-organization
Expert guidance for setting up and organizing research software projects following Sam Abbott's established patterns for R packages, Julia packages, and research projects
6