Results for “tree-test”

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Explore codebases efficiently using AST-based structural search, outline, and symbol unfolding to reduce token usage.

Token-optimized structural code search using tree-sitter AST parsing. Use instead of reading full files when you need to understand code structure, find functions, or explore a codebase efficiently.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Runs a relentless interview that asks every frontier question at once, round by round. Use when the user wants to be grilled on a design or map a design tree.

Botany Testing Advanced Skill

Restructure code while preserving behavior: confirm tests are green, refactor in small steps, keep tests green, review, and commit with a gated workflow.

Write effective unit tests with best practices for any project. Use when writing tests, creating test cases, improving test coverage, increasing confidence before release, or when the user mentions testing. Mutation score / assertion theater → test-mutation.

Safely change and test untested codebases using techniques from Feathers' 'Working Effectively with Legacy Code': seams, characterization tests, sprout/wrap, and dependency-breaking.

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

Applied Botany Testing Skill

Translates plain-language monitoring requests into deterministic watcher rule trees for the LaRuche system.

Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.

Brainstorm a longlist of benefits and costs for a project. Outputs two clean tables (benefits and costs), each with materiality (H/M/L), a cash flow tag (cash in / cash out / non-cash), a quantification method, and a monetisation method. Supports HMT Green Book, EU Better Regulation Guidelines, World Bank, Asian Development Bank, and the Victorian Treasury High Value High Risk (HVHR) framework.

Most teams run one test — expected peak for ten minutes — and believe they have

Triage mutation testing results by combining survived mutants, unnecessary test statements, and code graph analysis to identify false positives, missing test coverage, and fuzzing targets.

Analyzes test suites across multiple languages and tags each test with standardized traits (positive, negative, critical-path, etc.) for better test categorization and coverage visibility.

Use when inferring maximum-likelihood phylogenetic trees, selecting substitution models, running bootstrap support analyses, or performing partitioned phylogenetic analyses on sequence alignments.

Test-driven development for Laravel with PHPUnit and Pest, factories, database testing, fakes, and coverage targets.

Performs load testing with Locust, Python-based distributed testing, and real-time web UI.

Enforces a mandatory pre-commit/pre-PR testing gate: detects the test stack, runs the full suite, fixes failures, creates minimal tests when none exist, and verifies coverage before allowing commits.

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

Use for writing, reviewing, debugging, or testing Python terminal presentation built with Rich, including Console streams, Text and markup safety, tables, trees, panels, progress, status, Live displays, render protocols, and deterministic output capture. Do not use for CLI argument parsing, structured logging design, browser UI, or machine-readable protocol output that must remain plain.