- 📁 docs/
- 📁 notebooks/
- 📄 glama.json
- 📄 LICENSE
- 📄 llms.txt
Automatically discover novel, statistically validated patterns in tabular data. Find insights you'd otherwise miss, far faster and cheaper than doing it yourself (or prompting an agent to do it). Disco systematically searches for feature interactions, subgroup effects, and conditional relationships you wouldn't think to look for, validates each on hold-out data with FDR-corrected p-values, and checks every finding against academic literature for novelty. Returns structured patterns with conditions, effect sizes, citations, and novelty scores.
- 📁 references/
- 📄 README.md
- 📄 SKILL.md
Modern tidyverse patterns, style guide, and migration guidance for R development. Use this skill when writing R code, reviewing tidyverse code, updating legacy R code to modern patterns, or enforcing consistent style. Covers native pipe usage, join_by() syntax, .by grouping, pick/across/reframe operations, filter_out/when_any/when_all, recode_values/replace_values/replace_when, tidy selection, stringr patterns, naming conventions, and migration from base R or older tidyverse APIs. Use the R (btw) MCP tools to resolve function documentation and library references automatically.
Structured code review methodology for PRs. Prioritizes correctness, flags common anti-patterns, enforces scope discipline, checks test coverage, and provides actionable feedback. Language-agnostic. --- ## Skill: Code Reviewer You are running with the code-reviewer skill active. Apply a structured, evidence-based review methodology to every PR you review. ### Review Priorities Review in this order. Stop blocking on lower priorities if higher ones are clean. 1. **Correctness** — Does it solve the stated problem? Does it break existing behavior? 2. **Security** — Injection, auth issues, secret exposure 3. **Reliability** — Error handling, failure modes, edge cases 4. **Performance** — N+1 patterns, unnecessary allocations, algorithmic complexity 5. **Maintainability** — Readability, naming, patterns consistency 6. **Style** — Formatting, conventions (never block on style alone) ### Common Patterns to Flag #### Silent error swallowing - Empty `catch`/`except`/`rescue` blocks or ones that only log and continue - Ignored return values from fallible operations - Suppressed errors: `|| true`, `2>/dev/null`, bare `except: pass`, `_ = err` #### N+1 and loop inefficiency - API calls, database queries, or file reads inside loops - Missing eager loading / batch operations (e.g., `prefetch_related`, `include`, `DataLoader`, `JOIN`, batch API calls) - Repeated expensive computations that could be hoisted out of the loop #### Race conditions - Shared mutable state accessed from async or concurrent contexts without guards - Check-then-act patterns without atomicity (TOCTOU) - Missing locks, mutexes, or atomic operations on concurrent data access #### Boundary issues - Missing input validation at trust boundaries (user input, API responses) - Unsafe type casts or assertions without runtime checks - Off-by-one errors in range, slice, or index operations #### Backwards compatibility - Renamed or removed public APIs without migration path - Changed function signatures that break existi
Comprehensive project architecture blueprint generator that analyzes codebases to create detailed architectural documentation. Automatically detects technology stacks and architectural patterns, generates visual diagrams, documents implementation patterns, and provides extensible blueprints for maintaining architectural consistency and guiding new development.
