Explorar skills

Analyzes code change impact with risk scoring and affected-node mapping. Use before merging to understand what a change touches and what lacks test coverage.

Presents adaptive codebase challenge questions with multiple-choice and trace exercises. Use when testing contributor knowledge of the codebase.

Orchestrates multi-domain review (code, arch, tests, security) in a single pass. Use when comprehensive pre-release review is needed.

Generates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.

Creates clear, testable specifications from feature descriptions with user stories. Use when starting a new feature and needing a spec before planning.

Test skills via TDD in fresh subagents. Use when validating behavior or preventing bias.

Improves code quality across duplication, efficiency, and architectural fit. Use when code passes tests but quality is poor or before a major release.

Detailed development workflow with modular patterns for git, review, testing, and deployment.

Top password lists for authorized security testing: common passwords, darkweb leaks, worst passwords. Curated essentials (<10MB).

Defines testing quality metrics, coverage thresholds, and anti-patterns. Use when establishing test gates or validating a test suite's coverage targets.

Identify existing codebase patterns (naming conventions, architectural patterns, testing patterns) to maintain consistency. Use when generating code, reviewing changes, or understanding established practices.

Use when completing implementation, fixing bugs, refactoring code, or any time you need to verify the test suite passes. Also use when tests fail and you hear "pre-existing" or "not my changes" — enforces strict code ownership. Ensures MECE coverage (no overlap, no gaps) and that ALL test categories including E2E are executed.