docs
Check that all code has appropriate documentation.
Arguments: $ARGUMENTS (optional scope)
- commit: Check only staged files
- pr: Check all files changed in the current PR
- all: Check the entire codebase
- If no argument provided:
- If in a PR branch: defaults to 'pr'
- Otherwise: defaults to 'commit'
Phase 1: Scope Determination
- Determine scope based on $ARGUMENTS
Phase 2: Documentation Analysis
- Identify functions/classes lacking documentation
- Check quality of existing documentation
- Extract project documentation standards from CLAUDE.md
Phase 3: Documentation Updates
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