so101-biolab-automation

Audit and tighten codebase quality gates — lint, types, tests, code review. Use when onboarding a project, before a release, or when validation is too permissive.

Compacts verbose context into structured summary. Use after pollution sources (searches, logs, JSON) or at phase milestones.

Audits and aligns project documentation against its own declared hierarchy. Discovers authority chains from CONTRIBUTING.md (or equivalent), then detects broken links, duplicates, and misplaced content. Use when reviewing doc health, fixing stale references, or enforcing single-source-of-truth.

Implements concise, streamlined Python code matching exact architect specifications. Use when writing Python code, creating modules, or when the user asks to implement features in Python.

Investigates codebase before planning. Use before any non-trivial implementation task to gather context in isolation.

Provides concise, focused code reviews matching exact task complexity requirements. Use when reviewing code quality, security, or when the user asks for code review.

Writes tests following TDD (using pytest and Hypothesis) and BDD best practices. Use when writing unit tests, integration tests, or BDD scenarios.