Run any Skill in Manus with one click

kta-unit-test

Stars4

Forks0

UpdatedMay 5, 2026 at 18:01

Smart Kotlin unit testing with auto-detection, coverage analysis, and AI edge cases. Use when generating tests for biz/ layer classes, analyzing test coverage gaps, or discovering edge cases.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

dantech0xff

dantech0xff/dreams

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

5 files

SKILL.md

readonly

name	kta-unit-test
description	Smart Kotlin unit testing with auto-detection, coverage analysis, and AI edge cases. Use when generating tests for biz/ layer classes, analyzing test coverage gaps, or discovering edge cases.

Kotlin Unit Test

Project-specific skill for intelligent Kotlin unit testing.

When to Use

Generating tests for business logic classes (biz/ layer)
Analyzing test coverage gaps
Discovering edge cases for existing code
Before writing new tests to understand what's missing

Workflow

Analyze class: python scripts/analyze_kotlin.py units <file.kt>
Check coverage: python scripts/analyze_kotlin.py coverage <source_dir> <test_dir>
Discover edge cases: Load references/edge-case-discovery.md
Write tests: Follow patterns in references/test-patterns.md

Script Commands

# Analyze single file - extract testable units
python scripts/analyze_kotlin.py units app/src/main/.../SomeClass.kt

# Analyze coverage gaps between source and test directories
python scripts/analyze_kotlin.py coverage app/src/main/java/.../biz app/src/test/java/.../biz

Output Format

JSON structured output for parsing:

{
  "class_name": "SomeClass",
  "methods": [...],
  "dependencies": [...],
  "coverage": {"tested": [], "missing": []}
}

References

File	Purpose
`references/test-patterns.md`	JUnit4 + MockK + Turbine patterns
`references/edge-case-discovery.md`	AI prompts for finding edge cases

Integration

Works with .claude/agents/unit-test-agent.md for test generation workflow.

More from this repository

same repository

kta-code-review

dantech0xff/dreams

Senior Kotlin specialist code review — framework-agnostic. Use whenever the user asks to review, audit, critique, or get feedback on Kotlin code, a file, a class, a function, a module, a diff, a branch, a commit, or a pull request. Judges Kotlin language idioms, logic correctness, architecture and layering, concurrency (coroutines, Flow, structured concurrency, cancellation, race conditions), null safety, exception safety, testability, performance, and security. Detects force-unwraps, unchecked casts, GlobalScope, leaked mutability, broken structured concurrency, hidden side effects, weak abstractions, untestable seams, allocation hot spots, weak crypto, input-validation gaps, and PII logging. Outputs prioritized findings with file:line anchors and minimal-diff fixes. No assumptions about DI framework, UI framework, or build system.

2026-05-104

kta-compose-design-tokens

dantech0xff/dreams

Create Kotlin Compose design tokens from one of three supported sources — Google Stitch (MCP), Figma (MCP or JSON), or Codex Design (kta-design-spec output, Codex HTML/markdown artifacts). Three-layer architecture (Primitive/Semantic/Component) with code generation. Use when user asks to "generate design tokens", "create theme from Figma/Stitch/Codex design", "build Compose tokens from design spec", or "convert design source to tokens". Refuses any other input source and asks user for correct seed data.

2026-05-104

kta-compose-optimizer

dantech0xff/dreams

Optimize a single Jetpack Compose @Composable function. Use when the user wants to improve, polish, animate, or refactor ONE Composable — keywords like "optimize this composable", "make this smoother", "add animation to this", "split this composable", "fix recomposition", "this composable is laggy", "polish this UI", or when user pastes/points to a single @Composable function. Analyzes the target for recomposition issues, missing animations, size/concern splits, and stability problems, then iterates with the user via AskUserQuestion to pick which optimizations to apply, then delegates implementation to the kta-compose-developer agent and summarizes changes. Input MUST be exactly one Composable (file path + function name, or function name alone).

2026-05-104

kta-design-spec

dantech0xff/dreams

Per-screen design spec generator for AI design tools (Stitch / Figma AI / Codex artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.

2026-05-104

kta-idea-pipeline

dantech0xff/dreams

End-to-end Android indie idea workflow — feature-build phase only (no monetization). Phased — discover (if no idea) → generate 2 candidates → refine scope (offline/online, sharing, MVP vs full, core-value features) → risk/reward/tradeoff analysis when scoping down → emit idea brief. Use for greenfield app concepts, new feature ideation, idea discovery, or pre-design discovery before writing a design document. Triggers — new app idea, feature concept, indie dev brainstorm, validate idea, refine idea, what should I build, find an app idea, idea pipeline, I have no idea, help me find an app idea, scope down, MVP scoping, core value features.

2026-05-104

kta-module

dantech0xff/dreams

Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.

2026-05-104

name	kta-unit-test
description	Smart Kotlin unit testing with auto-detection, coverage analysis, and AI edge cases. Use when generating tests for biz/ layer classes, analyzing test coverage gaps, or discovering edge cases.

Kotlin Unit Test

Project-specific skill for intelligent Kotlin unit testing.

When to Use

Generating tests for business logic classes (biz/ layer)
Analyzing test coverage gaps
Discovering edge cases for existing code
Before writing new tests to understand what's missing

Workflow

Analyze class: python scripts/analyze_kotlin.py units <file.kt>
Check coverage: python scripts/analyze_kotlin.py coverage <source_dir> <test_dir>
Discover edge cases: Load references/edge-case-discovery.md
Write tests: Follow patterns in references/test-patterns.md

Script Commands

# Analyze single file - extract testable units
python scripts/analyze_kotlin.py units app/src/main/.../SomeClass.kt

# Analyze coverage gaps between source and test directories
python scripts/analyze_kotlin.py coverage app/src/main/java/.../biz app/src/test/java/.../biz

Output Format

JSON structured output for parsing:

{
  "class_name": "SomeClass",
  "methods": [...],
  "dependencies": [...],
  "coverage": {"tested": [], "missing": []}
}

References

File	Purpose
`references/test-patterns.md`	JUnit4 + MockK + Turbine patterns
`references/edge-case-discovery.md`	AI prompts for finding edge cases

Integration

Works with .claude/agents/unit-test-agent.md for test generation workflow.