Loading...
Loading...
Found 50 Skills
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
Go testing patterns and methodology: table-driven tests, t.Run subtests, t.Helper helpers, mocking interfaces, benchmarks, race detection, and synctest. Use when writing new Go tests, modifying existing tests, adding coverage, fixing failing tests, writing benchmarks, or creating mocks. Triggered by "go test", "_test.go", "table-driven", "t.Run", "benchmark", "mock", "race detection", "test coverage". Do NOT use for non-Go testing (use test-driven-development instead), debugging test failures (use systematic-debugging), or general Go development without test focus (use golang-general-engineer directly).
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when adding unit tests for a dbt model or practicing test-driven development (TDD) in dbt
Use when working with tdd workflows tdd cycle
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
Expert in Python testing with pytest and test-driven development
Master Bash Automated Testing System (Bats) for comprehensive shell script testing. Use when writing tests for shell scripts, CI/CD pipelines, or requiring test-driven development of shell utilities.
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.
Test-Driven Development specifically for Laravel applications using Pest PHP. Use when implementing any Laravel feature or bugfix - write the test first, watch it fail, write minimal code to pass.
Use this for development.
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.