Loading...
Loading...
Found 58 Skills
Refactor codebases using Design by Typed Holes methodology - iterative, test-driven refactoring with formal hole resolution, constraint propagation, and continuous validation. Use when refactoring existing code, optimizing architecture, or consolidating technical debt through systematic hole-driven development.
Root cause analysis for debugging. Use when bugs, test failures, or unexpected behavior have non-obvious causes, or after multiple fix attempts have failed.
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Creates language variants of existing Semgrep rules. Use when porting a Semgrep rule to specified target languages. Takes an existing rule and target languages as input, produces independent rule+test directories for each language.
Create high-quality ToolUniverse skills following test-driven, implementation-agnostic methodology. Integrates tools from ToolUniverse's 1,264+ tool library, creates missing tools when needed using devtu-create-tool, tests thoroughly, and produces skills with Python SDK + MCP support. Use when asked to create new ToolUniverse skills, build research workflows, or develop domain-specific analysis capabilities for biology, chemistry, or medicine.
Use when creating new skills, editing existing skills, or verifying if skills are valid before deployment
Systematically debug and diagnose issues methodically. Uses diagnostic techniques to identify root causes and implement fixes.
TDD feature build loop: spec (RED) → implement (GREEN) → refactor. Pass the feature name as argument.
Use when implementing a Beat change — requires gherkin or proposal artifact to be done first
TDD: enforce RED-GREEN-REFACTOR, tests before code.
Orchestrate parallel debugging agents with root-cause tracing for multi-failure scenarios
Applies TDD workflow to development. Use when writing tests before code, implementing features test-first, fixing bugs via failing test, or refactoring with test coverage. Detects AI anti-patterns.